On 6 March 2014 22:43, Noah Misch <n...@leadboat.com> wrote: > Good analysis. The hazards arise when pg_dump uses one of the ruleutils.c > deparse worker functions.
Ah, good. We're thinking along the same lines. I was already working on this analysis also. I'll complete mine and then compare notes. > One thing not to forget is that you can always get the old mutual exclusion > back by issuing LOCK TABLE just before a DDL operation. If some unlucky user > regularly gets pg_dump failures due to concurrent DROP TRIGGER, he has a > workaround. There's no comparable way for someone who would not experience > that problem to weaken the now-hardcoded AccessExclusiveLock. Good point. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers