Re: [GENERAL] pg_multixact issues
| От | Dev Kumkar |
|---|---|
| Тема | Re: [GENERAL] pg_multixact issues |
| Дата | |
| Msg-id | CALSLE1PzxeRd0RAmC20-X01TijiR-aSjxAVjfze6keW_iYMdCA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [GENERAL] pg_multixact issues (Dev Kumkar <devdas.kumkar@gmail.com>) |
| Список | pgsql-sql |
On Fri, Sep 26, 2014 at 1:36 PM, Dev Kumkar <devdas.kumkar@gmail.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 13224692Stumped ! 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...
В списке pgsql-sql по дате отправления: