Re: CREATE TABLE (with INHERITS) and ACCESS EXCLUSIVE locks - Mailing list pgsql-general

From Tom Lane
Subject Re: CREATE TABLE (with INHERITS) and ACCESS EXCLUSIVE locks
Date
Msg-id 13412.1144130019@sss.pgh.pa.us
Whole thread Raw
In response to CREATE TABLE (with INHERITS) and ACCESS EXCLUSIVE locks  ("Thomas F. O'Connell" <tfo@sitening.com>)
Responses Re: CREATE TABLE (with INHERITS) and ACCESS EXCLUSIVE locks  ("Thomas F. O'Connell" <tfo@sitening.com>)
List pgsql-general
"Thomas F. O'Connell" <tfo@sitening.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

pgsql-general by date:

Previous
From: "Thomas F. O'Connell"
Date:
Subject: CREATE TABLE (with INHERITS) and ACCESS EXCLUSIVE locks
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Create an index with a sort condition