Thu Jan 14 23:31:01 PST 2010
- Previous message: [Slony1-general] slony switchover & connection pooling tools
- Next message: [Slony1-general] Error in slony logs: relation "pg_catalog.pg_autovacuum" does not exist
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, We just upgraded one of the database to 8.4.2 using slony - 2.0.2. After the upgrade we are getting the following errors in slony logs: NOTICE: Slony-I: Logswitch to sl_log_1 initiated CONTEXT: SQL statement "SELECT "_inventorycluster".logswitch_start()" PL/pgSQL function "cleanupevent" line 101 at PERFORM 2010-01-14 23:15:59 PST INFO cleanupThread: 0.043 seconds for cleanupEvent() 2010-01-14 23:15:59 PST DEBUG1 cleanupThread: minxid: 4071 2010-01-14 23:16:00 PST ERROR cleanupThread: "select nspname, relname from "_inventorycluster".TablesToVacuum();" - ERROR: relation "pg_catalog.pg_autovacuum" does not exist LINE 1: select enabled from "pg_catalog".pg_autovacuum where vacreli... ^ QUERY: select enabled from "pg_catalog".pg_autovacuum where vacrelid = $1 CONTEXT: PL/pgSQL function "shouldslonyvacuumtable" line 25 at SQL statement PL/pgSQL function "tablestovacuum" line 6 at IF Can anybody let us know whats going wrong here. Regards, Nimesh. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20100115/7887bd6f/attachment.htm
- Previous message: [Slony1-general] slony switchover & connection pooling tools
- Next message: [Slony1-general] Error in slony logs: relation "pg_catalog.pg_autovacuum" does not exist
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list