Re: [GENERAL] Table not cleaning up drom dead tuples
| От | Jeff Janes |
|---|---|
| Тема | Re: [GENERAL] Table not cleaning up drom dead tuples |
| Дата | |
| Msg-id | CAMkU=1wcgS5Q2kP88NBduu8zr2Jsk52HWLx_HBrZJFADyjspxQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | [GENERAL] Table not cleaning up drom dead tuples (Антон Тарабрин <tarabanton@gmail.com>) |
| Ответы |
Re: [GENERAL] Table not cleaning up drom dead tuples
|
| Список | pgsql-general |
On Tue, Mar 14, 2017 at 5:09 AM, Антон Тарабрин <tarabanton@gmail.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@anarazel.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
В списке pgsql-general по дате отправления: