| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Jakob Egger <jakob(at)eggerapps(dot)at> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Refactor pg_dump as a library? |
| Date: | 2016-04-16 13:00:08 |
| Message-ID: | 57123758.4010506@proxel.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2016-04-16 14:15:56 | OS scheduler bugs affecting high-concurrency contention |
| Previous Message | Piotr Stefaniak | 2016-04-16 12:48:00 | Re: Small fix: avoid passing null pointers to memcpy() |