Re: Refactor pg_dump as a library? - Mailing list pgsql-hackers

From Andreas Karlsson
Subject Re: Refactor pg_dump as a library?
Date
Msg-id 57123758.4010506@proxel.se
Whole thread Raw
In response to Re: Refactor pg_dump as a library?  (David Steele <david@pgmasters.net>)
List pgsql-hackers
On 04/14/2016 07:28 PM, David Steele wrote:
> As far as I know pg_dump share locks everything before it starts so
> there shouldn't be issues with concurrent DDL.  Try creating a new
> inherited table with FKs, etc. during a pg_dump and you'll see lots of
> fun lock waits.

I am pretty sure that it does not lock functions, types or casts. So if 
you rename a function during pg_dump there should be a risk of getting a 
backup which will fail on restore.

Andreas




pgsql-hackers by date:

Previous
From: Piotr Stefaniak
Date:
Subject: Re: Small fix: avoid passing null pointers to memcpy()
Next
From: Kevin Grittner
Date:
Subject: OS scheduler bugs affecting high-concurrency contention