Re: CREATE TABLE (with INHERITS) and ACCESS EXCLUSIVE locks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: CREATE TABLE (with INHERITS) and ACCESS EXCLUSIVE locks
Date: 2006-04-04 05:53:39
Message-ID: 13412.1144130019@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Thomas F. O'Connell" <tfo(at)sitening(dot)com> writes:
> I'm dealing with an application that can potentially do ad hoc DDL.
> It uses a PG/pgSQL function, and the only DDL statements in the
> function are CREATE TABLE and CREATE INDEX statements. But I'm
> noticing that during the backup process (with pg_dump or pg_dumpall),
> the function is acquiring ACCESS EXCLUSIVE locks and bringing the
> application to its knees.

Please provide a test case. AFAIR neither of those should take any
AccessExclusive locks --- except on the new table, which shouldn't
matter because pg_dump won't see it.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-04-04 05:55:15 Re: Create an index with a sort condition
Previous Message Thomas F. O'Connell 2006-04-04 05:41:26 CREATE TABLE (with INHERITS) and ACCESS EXCLUSIVE locks