From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: pgsql-performance@postgresql.org
Subject: Re: What needs to be done for real Partitioning?
Date: Sun, 20 Mar 2005 01:16:23 +0100
Message-ID: <20050320001623.GA16805@uio.no> (raw)
In-Reply-To: <3375.1111276999@sss.pgh.pa.us>
References: <200503191202.38089.josh@agliodbs.com>
<18168.1111265368@sss.pgh.pa.us>
<200503191529.51794.josh@agliodbs.com>
<3375.1111276999@sss.pgh.pa.us>
On Sat, Mar 19, 2005 at 07:03:19PM -0500, Tom Lane wrote:
> Possibly, but I'm concerned about locking and deadlock issues. The
> reason that this is iffy is you would start the operation with only
> an INSERT-grade lock, and then discover that you needed to add a
> partition, which is surely something that needs an exclusive-grade
> lock (consider two sessions trying to add the same partition at the
> same time). So I don't see how to do it without lock upgrading,
> and lock upgrading is always a recipe for deadlocks.
What about letting something periodical (say, vacuum) do this?
/* Steinar */
--
Homepage: http://www.sesse.net/
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-performance@postgresql.org
Cc: sgunderson@bigfoot.com
Subject: Re: What needs to be done for real Partitioning?
In-Reply-To: <20050320001623.GA16805@uio.no>
* 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