We have discovered an interesting locking scenario with Slony-I that
is pointing to a use for the ability to exclude certain schemas from
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.
Everything else then falls behind that, as they are waiting for the
lock to get dropped off.
The solution is easy enough, in that (at present) the interesting data
is in a single database schema.
does the trick.
What would be nice would be the ability to consciously _exclude_
schemas, where the nice way would be --exclude-schema=_slony_schema
If someone has some "round tuits," I'll have to catch up on sleep...
(format nil "~S(at)~S" "cbbrowne" "ntlug.org")
Save your burned out bulbs for me, I'm building my own dark room.
pgsql-hackers by date
|Next:||From: Gaetano Mendola||Date: 2004-09-15 21:04:11|
|Subject: Re: x86_64 configure problem|
|Previous:||From: Simon Riggs||Date: 2004-09-15 20:50:17|
|Subject: Re: some PITR performance data with DBT-2|