From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [SQL] pg_multixact issues |
Date: | 2014-09-30 15:10:28 |
Message-ID: | CALSLE1PzxeRd0RAmC20-X01TijiR-aSjxAVjfze6keW_iYMdCA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-sql |
On Fri, Sep 26, 2014 at 1:36 PM, Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> wrote:
> Received the database with huge pg_multixact directory of size 21G and
> there are ~82,000 files in "pg_multixact/members" and 202 files in
> "pg_multixact/offsets" directory.
>
> Did run "vacuum full" on this database and it was successful. However now
> am not sure about pg_multixact directory. truncating this directory except
> 0000 file results into database start up issues, of course this is not
> correct way of truncating.
> FATAL: could not access status of transaction 13224692
>
> Stumped ! Please provide some comments on how to truncate pg_multixact
> files and if there is any impact because of these files on database
> performance.
>
Facing this issue on couple more machines where pg_multixact is huge and
not being cleaned up. Any suggestions / troubleshooting tips?
Regards...
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-09-30 15:20:13 | Re: [SQL] pg_multixact issues |
Previous Message | pbj | 2014-09-30 14:00:28 | Re: BDR Global Sequences |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-09-30 15:17:11 | Re: pgcrypto: PGP armor headers |
Previous Message | Bruce Momjian | 2014-09-30 14:56:51 | Re: Collations and Replication; Next Steps |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-09-30 15:20:13 | Re: [SQL] pg_multixact issues |
Previous Message | David G Johnston | 2014-09-29 21:18:23 | Re: Why data returned inside parentheses in for loop |