Re: [GENERAL] Table not cleaning up drom dead tuples
От | Антон Тарабрин |
---|---|
Тема | Re: [GENERAL] Table not cleaning up drom dead tuples |
Дата | |
Msg-id | CAJH0_XsJpu5YnGLu=06Yp7+jE67gyXSL1GivzYy9ow4EvHzb8A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [GENERAL] Table not cleaning up drom dead tuples (Jeff Janes <jeff.janes@gmail.com>) |
Список | pgsql-general |
That was exactly that one bug. Thanks a lot
вт, 14 марта 2017 г., 23:26 Jeff Janes <jeff.janes@gmail.com>:
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.3Are you using replication slots?See this, fixed in 9.5.5:commit de396a1cb34626619ddc6fb9dec6d12abee8b589Author: Andres Freund <andres@anarazel.de>Date: Wed Aug 17 13:15:03 2016 -0700Properly re-initialize replication slot shared memory upon creation.Slot creation did not clear all fields upon creation. After start thememory is zeroed, but when a physical replication slot was created inthe shared memory of a previously existing logical slot, catalog_xminwould not be cleared. That in turn would prevent vacuum from doing itsduties.Cheers,Jeff
--
___________________________
С наилучшими пожеланиями,
Антон Тарабрин
With best regards,
Anton Tarabrin
В списке pgsql-general по дате отправления: