Wed Feb 10 01:47:26 PST 2010
- Previous message: [Slony1-general] slony fails after upgrade from 8.2 to 8.4
- Next message: [Slony1-general] slony fails after upgrade from 8.2 to 8.4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
On Tue, Feb 09, 2010 at 02:14:19PM +0100, Koen Martens wrote:
> 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)
To answer my own question: it seems there is some lingering cache somehwere,
as a restart of PostgreSQL before re-installing slony did the trick.
Gr,
Koen
- Previous message: [Slony1-general] slony fails after upgrade from 8.2 to 8.4
- Next message: [Slony1-general] slony fails after upgrade from 8.2 to 8.4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list