Jesper Engman writes:
> I wonder if there is a small time span between when pg_dump starts and
> when all locks have been acquired that may be the problem (if a table
> is dropped during that time span). Is there such a small time of
> vulnerability?
Certainly. pg_dump has to read pg_class to ge
DDL is not excluded from MVCC, right? This kind of concurrency should
be handled and it's generally managed just fine. I just did a lab test
attempting to drop a table while pg_dump is running on the same db and
it simply waits to drop the table until pg_dump is done. That is the
expected behavior.
On Thu, Aug 18, 2011 at 2:05 AM, Jesper Engman wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6167
> Logged by: Jesper Engman
> Email address: jes...@engman.net
> PostgreSQL version: 8.3.10
> Operating system: Linux
> Description: pg_dump fails
