That was exactly that one bug. Thanks a lot вт, 14 марта 2017 г., 23:26 Jeff Janes <jeff.ja...@gmail.com>:
> On Tue, Mar 14, 2017 at 5:09 AM, Антон Тарабрин <taraban...@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 <and...@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 > -- ___________________________ С наилучшими пожеланиями, Антон Тарабрин With best regards, Anton Tarabrin
