Steve Simms <steve at deefs.net> writes:
> In order to combine steps 5-8, I've just finished adding a switch to
> altperl/subscribe_set.pl that copies the schema over to the
> destination before creating the slonik script.
>
> Before I commit this, I would love to know if this is something others
> would like, and if there are any major problems with it.

Others have made some useful suggestions surrounding the handling of
ordering of operations which strike me as being very useful.

I have a few thoughts to add:

0.  I agree with Josh that it's probably a bad idea to mangle pg_dump
    output because you can't depend on its ordering.  

    His comment that the format "*will* change" isn't actually strong
    enough; it's fair to say that Slony-I needs to support multiple
    formats _already_ because the formats differ between 7.3, 7.4, and
    8.0 due to the very same issue of relational dependancies.

1.  You might also take a look at Jan's script "slony1_dump.sh", in
    the tools directory, which prepares a log shipping schema.

2.  I would think the more parsimonious approach would be to create a
    whole new script, altperl/dump_schema.pl rather than making
    subscribe_set.pl more complex.  subscribe_set.pl could always
    _call_ dump_schema.pl, but having it separate permits it to be used 
    for things other than just establishing subscriptions.

3.  I presume that the script goes to the origin to get the schema,
    right?
-- 
"cbbrowne","@","ca.afilias.info"
<http://dev6.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)