Re: pg_dump --exclude-schema=foo

Quoth tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane):
> Chris Browne <cbbrowne(at)acm(dot)org> writes:
>> We have discovered an interesting locking scenario with Slony-I that
>> is pointing to a use for the ability to exclude certain schemas from
>> pg_dump.
>
>> The situation is that when a "full" pg_dump kicks off, a Slony-I
>> "create sync" event, which expects to "LOCK slony_schema.sl_event;",
>> is blocked from getting the exclusive lock that it desires.
>
> Perhaps this should be seen as a Slony bug. Does it really need an
> AccessExclusive lock, or would an Exclusive lock do?

You could be right; that's still To Be Determined.

It nonetheless appears like a useful idea in general to be able to
specify inclusion/exclusion of multiple schemas.
--
(reverse (concatenate 'string "gro.mca" "@" "enworbbc"))
http://www.ntlug.org/~cbbrowne/languages.html
"You can only examine 10 levels of pushdown, because that's all the
fingers you have to stick in the listing."
-- Anonymous programmer - "TOPS-10 Crash Analysis Guide"