From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Антон Тарабрин <tarabanton(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Table not cleaning up drom dead tuples |
Date: | 2017-03-14 20:26:14 |
Message-ID: | CAMkU=1wcgS5Q2kP88NBduu8zr2Jsk52HWLx_HBrZJFADyjspxQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Mar 14, 2017 at 5:09 AM, Антон Тарабрин <tarabanton(at)gmail(dot)com>
wrote:
> Good day. It seems that we have some strange case of VACUUM malfunction
> and table bloating.
>
> PostgreSQL 9.5.3
>
Are you using replication slots?
See this, fixed in 9.5.5:
commit de396a1cb34626619ddc6fb9dec6d12abee8b589
Author: Andres Freund <andres(at)anarazel(dot)de>
Date: Wed Aug 17 13:15:03 2016 -0700
Properly re-initialize replication slot shared memory upon creation.
Slot creation did not clear all fields upon creation. After start the
memory is zeroed, but when a physical replication slot was created in
the shared memory of a previously existing logical slot, catalog_xmin
would not be cleared. That in turn would prevent vacuum from doing its
duties.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Lawrence Cohan | 2017-03-14 20:37:11 | Re: Postgres backup solution |
Previous Message | Alexander Farber | 2017-03-14 20:25:10 | Re: UPDATE ... ON CONFLICT DO NOTHING |