Re: pg_dump --exclude-schema=foo - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump --exclude-schema=foo
Date
Msg-id 29042.1095357394@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump --exclude-schema=foo  (Chris Browne <cbbrowne@acm.org>)
List pgsql-hackers
Chris Browne <cbbrowne@acm.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?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: subtransaction assert failure
Next
From: Tom Lane
Date:
Subject: Re: Problems with SPI memory management