On Fri, Jul 3, 2009 at 6:06 PM, Pedro Doria
Meunier<pdoria at netmadeira.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Andrew,
>
> This bit: http://www.slony.info/documentation/stmtmergeset.html

Is this actually the documentation you wanted to cite? It makes no
reference to DDL or execute script at all.

The execute script documentation
(http://www.slony.info/documentation/stmtddlscript.html) description
starts with 'Executes a script containing arbitrary SQL statements on
all nodes' so the documentation seems clear enough.

To 'create a new table' (create a new table on all nodes and add it to
an existing replication set).

 - create the table using EXECUTE SCRIPT or execute manually on all nodes
 - create a new replication set with the same origin as the target
replication set.
 - add the table and any sequences to the new replication set
 - subscribe the new replication set to nodes so the subscription list
is identical to the target replication sets subscription list.
 - wait for sync
 - merge the new replication set into the target replication set using
MERGE SET.

(I wish Slony-I had ADD TABLE so we didn't all have to implement this
logic in our maintenance tools...)


>>> Contrary to what's stated in the documentation, execute script
>>> **seems** to propagate DDL changes (new objects) throughout the
>>> replication set.
>>
>> What part of the documentation gave you the impression that execute
>>  script wouldn't send DDL through the system?  That's the way you
>> put DDL changes in, in fact.


-- 
Stuart Bishop <stuart at stuartbishop.net>
http://www.stuartbishop.net/