From: Constantin S. Pan <kvapen@gmail.com>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Grigory Smolkin <g.smolkin@postgrespro.ru>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Subject: Re: Fun fact about autovacuum and orphan temp tables
Date: Fri, 21 Oct 2016 13:08:58 +0300
Message-ID: <20161021130858.620751f1@ppg> (raw)
In-Reply-To: <CAB7nPqTmeDmf4+LjQMBAKDWfPXO28cF7aL-5JGWKegyNQG_LLA@mail.gmail.com>
References: <7b7f3e98-9753-3fa9-aaa4-b6f8a766c251@postgrespro.ru>
<20161020153024.19cbc758@ppg>
<CAB7nPqTmeDmf4+LjQMBAKDWfPXO28cF7aL-5JGWKegyNQG_LLA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On Fri, 21 Oct 2016 14:29:24 +0900
Michael Paquier <michael.paquier@gmail.com> wrote:
> That's invasive. I am wondering if a cleaner approach here would be a
> flag in deleteOneObject() that performs the lock cleanup, as that's
> what you are trying to solve here.
The problem occurs earlier, at the findDependentObjects step. All the
objects inside the namespace are being locked before any of them gets
deleted, which leads to the "too many locks" condition.
Cheers,
Constantin Pan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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-hackers@postgresql.org
Cc: kvapen@gmail.com, michael.paquier@gmail.com, g.smolkin@postgrespro.ru
Subject: Re: Fun fact about autovacuum and orphan temp tables
In-Reply-To: <20161021130858.620751f1@ppg>
* 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