Jeff Frost <jeff at frostconsultingllc.com> writes:
> For extra background on this bug, see the thread here:
> http://lists.slony.info/pipermail/slony1-general/2007-September/006687.html
>
> This is on Slony1-1.2.10, PostgreSQL-8.1.9:
>
> I've run into a situation on a client cluster composed of a master and
> 2 slave nodes where a deadlock on one of the slaves happens quite
> regularly during any EXECUTE SCRIT commands.  It seems if slony loses
> the deadlock, some of the tables are left in a not altered for
> replication state and this breaks replication.

I'm going to set up (heh) a test case, let's call it
"testdeadlockddl", which will try to "tickle" this problem.

The approach:

- I'll start by creating a set that is replicated, and where some data
  is flowing thru.

- I'll set up some queries against the replica in order to try to
  encourage deadlocks.

- Then an "EXECUTE SCRIPT" will try adding a new table.  As a side effect,
  it will implicitly require locks on all the replicated tables.

I don't see that there are other particular details to this, right?
-- 
let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;;
http://www3.sympatico.ca/cbbrowne/linuxxian.html
A  student,  in hopes  of  understanding  the  Lambda-nature, came  to
Greenblatt.  As they spoke a  Multics system hacker walked by.  "Is it
true", asked the  student, "that PL-1 has many of  the same data types
as  Lisp?"   Almost before  the  student  had  finished his  question,
Greenblatt shouted, "FOO!", and hit the student with a stick.