Hello.

Possibly this fact needs to be included in the documentation?

Steps to reproduce:

1. Create table with name "b" on slave manually (emulate an error of broken
replication, see below).
2. Check that there is no table "b" on master.
3. Run via slonik's EXECUTE DDL within TRY block (in the single
transaction):

CREATE TABLE a(id INTEGER);
CREATE TABLE b(id INTEGER);

4. On master, this query successfully finishes. On slave, only table "a" is
created (and committed!), but "b" is not (it already exists).
5. Conclustion: on master, "a" and "b" are created within the single
transaction. On slave, "a" and "b" are created within different
transactions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20090321/=
14e9690b/attachment.htm