On 10/21/2004 11:28 AM, Peter Nelson wrote:

> Hi,
> 
> Just two days I setup 1.0.2, so I guess the new release was bound to
> happen ;)
> 
> Anyway, I've been bad and added a few fields to a table that's being
> replicated. Is it enough to recreate the trigger on the table with the
> appropriate number of 'v's as the last parameter, or should I do
> something else?

You should have RTFM before being that nasty to your database - Slony 
provides a DDL script execution mechanism especially to do that for you 
in a safe way. See

http://gborg.postgresql.org/project/slony1/genpage.php?slonik_commands#stmt_ddl_script

The best way would be to rebuild your Slony cluster, now that you have 
done it wrong already. And it would be the only way in case the table 
got already updated with that new attributes in place, because those 
items did not get replicated.

If you are 100% sure that this hasn't happened and that the table is 
still in sync and the same attributes have been added in the same order 
on all subscribers, you could execute a sequence of

     start transaction;
     select _<clustername>.alterTableRestore(<table-id>);
     select _<clustername>.alterTableForReplication(<table-id>);
     commit;

on all nodes.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #