On Tue, Feb 09, 2010 at 02:14:19PM +0100, Koen Martens wrote:
> I'm having a strange problem. We have just upgraded a database from 8.2.x
> to 8.4.2 (both master and slave). We did a pg_dumpall from the 8.2 install,
> which was configured as a slony master, and imported that into the fresh
> 8.4.2. 
> 
> I then removed the slony schema from the database in question and started
> configuration of slony afresh. However, after initializing the slony replication
> (defining the sets, nodes and paths) but before starting the replication, we
> get errors:
> 
> Feb  9 13:40:58 dbmain postgres[38232]: [404-1] ERROR:  cache lookup failed for type 30549603
> Feb  9 13:40:58 dbmain postgres[38232]: [404-2] CONTEXT:  SQL statement "INSERT INTO _live.sl_log_1 (log_origin, log_xid, log_tableid, log_actionseq, log_cmdtype, log_cmddata) VALUES (1, $1, $2, nextval('_live.sl_action_seq'), $3, $4);"
> Feb  9 13:40:58 dbmain postgres[38232]: [404-3] STATEMENT:  UPDATE passports
> Feb  9 13:40:58 dbmain postgres[38232]: [404-4]                                 SET ps_expires=TO_TIMESTAMP('20100210062058', 'YYYYMMDDHH24MISS')
> Feb  9 13:40:58 dbmain postgres[38232]: [404-5]                                 WHERE (ps_id=$1)
> 
> This effectively blocks transactions (which is bad because this database is
> in production).
> 
> I thus removed the slony schema again (drop schema _live cascade) and things
> are fine again. However, we're now running without replication, that's scary.
> 
> Any hints would be much appreciated!

One more thing, this is with slony 1.2.20.

Gr,

Koen