Re: [SQL] pg_multixact issues
| От | Dev Kumkar |
|---|---|
| Тема | Re: [SQL] pg_multixact issues |
| Дата | |
| Msg-id | CALSLE1MAgy4QC0-xLju6MBxO6Upp6=84xwAMt2dkfiGbd6pB9Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [SQL] pg_multixact issues (Dev Kumkar <devdas.kumkar@gmail.com>) |
| Ответы |
Re: [SQL] pg_multixact issues
Re: [SQL] pg_multixact issues |
| Список | pgsql-general |
On Wed, Sep 17, 2014 at 7:20 PM, Dev Kumkar <devdas.kumkar@gmail.com> wrote:
On Wed, Sep 17, 2014 at 6:51 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:http://www.postgresql.org/docs/9.3/static/routine-vacuuming.html#VACUUM-FOR-MULTIXACT-WRAPAROUND
Looked into these details. Can there be an example explained that will really help to understand this in practice?
Also one additional information here, the database was restarted various times. But still the pg_multixact directory size is increasing.
Actually there were multiple updates happening in different processes which lead to the locking issues and landed up into this situation.
Actually there were multiple updates happening in different processes which lead to the locking issues and landed up into this situation.
How can I recover the system at this stage and also clean up pg_multixact gracefully?
Regards...
В списке pgsql-general по дате отправления: