Re: pg_dump --exclude-schema=foo

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org, Jan Wieck <JanWieck(at)Yahoo(dot)com>
Subject: Re: pg_dump --exclude-schema=foo
Date: 2004-09-16 17:56:34
Message-ID: 29042.1095357394@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-09-16 18:12:40 Re: [HACKERS] Problems with SPI memory management
Previous Message Tom Lane 2004-09-16 15:43:17 Re: subtransaction assert failure