On Tue, 2005-05-10 at 16:57, Christopher Browne wrote:
> Scott Marlowe wrote:
> >>In any case, logs for node #2 are vital to the diagnosis.
> >>    
> >>
> >
> >Should I turn up the verbosity a bit in the logging and see if I can get
> >more data?  I'll try to figure out exactly what in the ddl script is
> >breaking the update...
> >  
> >
> Yes, that would presumably be useful.

Turned it up to debug1, got nothing more... sigh.

> The clever idea that one of our guys came up with is that you should
> test DDL changes in a sort of "two phase" manner...
> 
> 1.  Submit the scripts directly, inside a BEGIN clause, which is then
> rolled back, on the "master."

It runs without errors on the master, that I know from previous testing.

> 2.  Submit the script with BEGIN/work/ROLLBACK via Slonik.  That should
> behave as a no-op, but show off any errors you might hit with it WITHOUT
> having it take effect partially on your nodes.

I'll try that.

> After those two steps, you run it in full blown fashion.
> 
> DDL is pretty scary, all in all...

No arguments on this front.  :)  Thx for the help.