From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Cristian Cruz <danielcristian@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: DROP TABLE waiting for pg_dump
Date: Thu, 02 Oct 2008 08:11:45 -0400
Message-ID: <23223.1222949505@sss.pgh.pa.us> (raw)
In-Reply-To: <48d0cacb0810020433k1eadf01ckaee4990fc25ab5c6@mail.gmail.com>
References: <48d0cacb0810020433k1eadf01ckaee4990fc25ab5c6@mail.gmail.com>
"Daniel Cristian Cruz" <danielcristian@gmail.com> writes:
> I had a problem today, where pg_dump was locking a concurrent DROP TABLE,
> and it was another table, not the table in the COPY running. Is it normal?
Yes. pg_dump acquires ACCESS SHARE lock on all the tables it's
intending to dump. Without that it couldn't guarantee a consistent
dump.
regards, tom lane
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, danielcristian@gmail.com
Subject: Re: DROP TABLE waiting for pg_dump
In-Reply-To: <23223.1222949505@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