Re: [GENERAL] pg_multixact issues - Mailing list pgsql-sql

From Dev Kumkar
Subject Re: [GENERAL] pg_multixact issues
Date
Msg-id CALSLE1Pe22dK8ULkGEQd3X3jOrA32Xs2zkxU2OAaUOTU4z+a0Q@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] pg_multixact issues  (Dev Kumkar <devdas.kumkar@gmail.com>)
Responses Re: [GENERAL] pg_multixact issues  (Dev Kumkar <devdas.kumkar@gmail.com>)
List pgsql-sql
On Fri, Sep 19, 2014 at 1:23 PM, Dev Kumkar <devdas.kumkar@gmail.com> wrote:
Apologies for the delay, was working/troubleshooting same issue and was away from my emails. :(
Regards...

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.

Regards...

pgsql-sql by date:

Previous
From: Ian Lawrence Barwick
Date:
Subject: Re: uuid for each postgres install?
Next
From: Gerardo Herzig
Date:
Subject: how to see "where" SQL is better than PLPGSQL