On Mon, 29 Jan 2007, Casey Duncan wrote:

> I recently upgraded to slony 1.2.6. We were rehearsing a database
> schema upgrade for a two node slony cluster and came across an error
> at the end. We need to avoid having the execute script do its
> exclusive locks with the application talking to the database, so we
> do it using the following dance:
>
> 1. Turn off slon daemons
> 2. Switch application to use the secondary (read-only of course)
> 3. Run the upgrade script on the primary using execute script and add
> tables & sequences into a new set and merge waiting for subscriptions
> to be confirmed (which blocks).
> 4. Switch the application back to the primary db
> 5. Turn the slon daemons back on (which unblocks #3).
>
> All was well until step #5 when we got this error:
> <stdin>:12: PGRES_FATAL_ERROR select "_radio".mergeSet(1, 9999);  -
> ERROR:  Slony-I: set 9999 has subscriptions in progress - cannot merge

Did the DDL changes complete on the slave?  I'm wondering if they got lost 
because the slon was not running at the time the DDL changes were submitted.


> 2007-01-29 16:41:56 PST ERROR  remoteWorkerThread_1: Could not find
> table "public"."new_table1" on subscriber

Does public.new_table1 actually exist on the slave?

>
> Any insights are appreciated. I'll be trying to reproduce this in a
> bit more isolated environment too.

-- 
Jeff Frost, Owner 	<jeff at frostconsultingllc.com>
Frost Consulting, LLC 	http://www.frostconsultingllc.com/
Phone: 650-780-7908	FAX: 650-649-1954