On 09/17/2014 01:36 PM, Dev Kumkar wrote:
On Wed, Sep 17, 2014 at 7:20 PM, Dev Kumkar <devdas.kum...@gmail.com <mailto:devdas.kum...@gmail.com>> wrote:On Wed, Sep 17, 2014 at 6:51 PM, Adrian Klaver <adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>> wrote: http://www.postgresql.org/__docs/9.3/static/routine-__vacuuming.html#VACUUM-FOR-__MULTIXACT-WRAPAROUND <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. How can I recover the system at this stage and also clean up pg_multixact gracefully?
Aaah, hit enter too soon. Also see the other changes under Changes that apply to multixact in 9.3.5
Regards...
-- Adrian Klaver adrian.kla...@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
