| From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, pgsql-sql(at)postgresql(dot)org |
| Subject: | pg_multixact issues |
| Date: | 2014-09-17 12:16:05 |
| Message-ID: | CALSLE1P4knmyFa5BzdeYo7fVnjw-1-TwW9dXTEW-9nJjK4fQMg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-sql |
Hello,
On one my machine the pg_multixact directory size has grown up to 5 GB and
am not sure how to clean up this directory.
From the storage-file-layout this directory contains multitransaction
status data.
pg_multixactSubdirectory containing multitransaction status data (used for
shared row locks)
It would really help if someone can provide some reading material regarding
pg_multixact? Would this also result in database slowness by any chance?
Are there any tweaking commands related to this directory settings, also
how can I cleanup/truncate this directory without impacting the overall
database.
Looking forward to get some insight here.
Regards...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-09-17 13:21:47 | Re: pg_multixact issues |
| Previous Message | Martin Waite | 2014-09-17 10:03:42 | encoding confusion with \copy command |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2014-09-17 12:27:02 | [Windows,PATCH] Use faster, higher precision timer API |
| Previous Message | Andres Freund | 2014-09-17 11:45:58 | Re: removing volatile qualifiers from lwlock.c |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-09-17 13:21:47 | Re: pg_multixact issues |
| Previous Message | Kamal Kumar TRR | 2014-09-15 10:43:51 | Re: How to compare two tables in PostgreSQL |