From: Ondřej Světlík <osvetlik@flexibee.eu>
To: pgsql-admin@postgresql.org
Subject: Re: Autovacuum of pg_shdepend
Date: Wed, 4 May 2016 22:27:30 +0200
Message-ID: <572A5B32.4050302@flexibee.eu> (raw)
In-Reply-To: <17376.1462388827@sss.pgh.pa.us>
References: <20160504152518.GA102195@alvherre.pgsql>
<17376.1462388827@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Dne 4.5.2016 v 21:07 Tom Lane napsal(a):
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> Ooh, interesting bug.
>
>> As a workaround I suggest connecting to all of your databases except one
>> and disabling autovacuum for pg_shdepend. Then the table will be
>> processed in the one database where you left it enabled, and the other
>> workers will take care of the rest of the tables.
>
>> I'll think about a real fix.
>
> Seems like a simple answer is to consider all shared catalogs to "belong"
> to only one database for autovac purposes, ie, only autovac workers in
> that database would consider vacuuming them. The problem IIUC is that the
> interlock against multiple workers glomming onto the same table only
> considers other workers in the same DB.
>
> The fun part might be to decide which DB that is. I don't think we should
> depend on any of the standard databases always being there.
>
> regards, tom lane
>
How about a new configuration option, something like
#autovacuum_maintenance_database = postgres
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
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: osvetlik@flexibee.eu
Subject: Re: Autovacuum of pg_shdepend
In-Reply-To: <572A5B32.4050302@flexibee.eu>
* 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