From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Ondřej Světlík <osvetlik@flexibee.eu>
Cc: pgsql-admin@postgresql.org
Subject: Re: Autovacuum of pg_database
Date: Mon, 09 May 2016 18:30:47 -0400
Message-ID: <4023.1462833047@sss.pgh.pa.us> (raw)
In-Reply-To: <20160509213030.GA496423@alvherre.pgsql>
References: <20160509213030.GA496423@alvherre.pgsql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Now that I actually tried this, it turned out that this problem is not
> so simple. vacuum.c already has logic to use conditional acquire of the
> table-level lock, and if not available it skips the table:
> LOG: skipping vacuum of "pg_shdepend" --- lock not available
> so an autovacuum worker is never "stuck" behind another worker trying to
> vacuum the table.
Hmm ... but then, how do we have the observed symptom of several workers
concurrently trying to process the same shared catalog? Seems like all
but one should fall out at this point.
regards, tom lane
--
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: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, osvetlik@flexibee.eu
Subject: Re: Autovacuum of pg_database
In-Reply-To: <4023.1462833047@sss.pgh.pa.us>
* 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