From: Vicky Soni - Quipment India <vicky.soni@quipment.nl>
To: Ondřej Světlík <osvetlik@flexibee.eu>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Autovacuum of pg_database
Date: Fri, 6 May 2016 06:26:03 +0000
Message-ID: <9241fe3d6b8f46758b67dcfbee479ac8@Strand.quipment.local> (raw)
In-Reply-To: <572B6D6A.5090106@flexibee.eu>
References: <20160505154341.GA177987@alvherre.pgsql>
<572B6D6A.5090106@flexibee.eu>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Hello,
In my development setup I promoted slave, and now autovacuum keep running again and again.
Specially on pg_statistics table of one of my OLTP using many temp tables in functions.
Please help.
Thanks & Regards,
Vicky Soni
Database Administrator
-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Ondrej Svetlík
Sent: 05 May 2016 21:28
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Autovacuum of pg_database
Dne 5.5.2016 v 17:43 Alvaro Herrera napsal(a):
> Ondřej Světlík wrote:
>> Dne 5.5.2016 v 17:19 Ondřej Světlík napsal(a):
>>> Dne 5.5.2016 v 17:16 Ondřej Světlík napsal(a):
>>>> Hello again,
>>>>
>>>> we have another strange problem with autovacuum. The process goes
>>>> well until it reaches the table pg_database (in some databases, not
>>>> all), then it loops over it forever (until I run vacuum full
>>>> analyze on that table, simple vacuum doesn't help):
>>>>
>>>> 2016-05-05 17:13:33 CEST 34818LOG: automatic vacuum of table
>>>> "somedatabase.pg_catalog.pg_database": index scans: 0
>>>> pages: 0 removed, 233 remain
>>>> tuples: 0 removed, 5817 remain, 0 are dead but not yet removable
>>>> buffer usage: 87 hits, 0 misses, 0 dirtied
>>
>> And now the same goes for pg_authid. Sorry for spamming, I hope this
>> is the last one.
>
> These are all shared catalogs. There are others, so you may still see
> more. We got another report for pg_database
> https://www.postgresql.org/message-id/A9D40BB7-CFD6-46AF-A0A1-249F0487
> 8A2A%40amazon.com so I suppose there really is a bug. I don't know
> what's going on there.
>
Let me know if I can help trace the cause.
With regards
Ondřej
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: vicky.soni@quipment.nl, osvetlik@flexibee.eu
Subject: Re: Autovacuum of pg_database
In-Reply-To: <9241fe3d6b8f46758b67dcfbee479ac8@Strand.quipment.local>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox