Re: 8.2 Autovacuum BUG ?

Hi Álvaro Herrera, Please find the corresponding output: *1).select name, setting, source, sourcefile, sourceline from pg_settings where name like '%vacuum%'; * -[ RECORD 1 ] name | autovacuum setting| on source | configuration file

Re: 8.2 Autovacuum BUG ?

Please show the output of these queries in the relevant databases: select name, setting, source, sourcefile, sourceline from pg_settings where name like '%vacuum%'; select oid::regclass, reloptions from pg_class where reloptions is not null; -- Álvaro Herrera

Re: 8.2 Autovacuum BUG ?

On Wed, Jan 24, 2018 at 7:48 AM, Pavan Teja wrote: > > > Yes, but why doing vacuum freeze of a table is causing a rapid > ​archiving?? > Any idea?? > > IIUC ​Freezing involves physically altering those pages that are not frozen to make them frozen. Those

Re: 8.2 Autovacuum BUG ?

On Jan 24, 2018 7:57 PM, "Claudio Freire" wrote: On Wed, Jan 24, 2018 at 8:50 AM, pavan95 wrote: > Hello all, > > One more interesting observation made by me. > > I have ran the below query(s) on production: > > SELECT > relname, >

Re: 8.2 Autovacuum BUG ?

On Wed, Jan 24, 2018 at 8:50 AM, pavan95 wrote: > Hello all, > > One more interesting observation made by me. > > I have ran the below query(s) on production: > > SELECT > relname, > age(relfrozenxid) as xid_age, > pg_size_pretty(pg_table_size(oid)) as

pg_xlog unbounded growth

Hello, This email is structured in sections as follows: 1 - Estimating the size of pg_xlog depending on postgresql.conf parameters 2 - Cleaning up pg_xlog using a watchdog script 3 - Mailing list survey of related bugs 4 - Thoughts We're using PostgreSQL 9.6.6 on a Ubuntu 16.04.3 LTS. During