Wed Mar 20 16:54:21 PDT 2013
- Previous message: [Slony1-bugs] [Bug 286] PG 9.3 has changed LookupExplicitNamespace to take two arguments
- Next message: [Slony1-bugs] [Bug 287] UPDATE FUNCTIONS in 2.2 doesn't work
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=287 Summary: UPDATE FUNCTIONS in 2.2 doesn't work Product: Slony-I Version: devel Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: low Component: slonik AssignedTo: slony1-bugs at lists.slony.info ReportedBy: ssinger at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 When updating a slony 2.2.0 b1 instance to 2.2.0 B3 We get the following update functions(id=1); <stdin>:2: PGRES_FATAL_ERROR select max(ev_seqno) FROM "_test".sl_event , "_test".sl_node where ev_origin="_test".getLocalNodeId('_test') AND ev_type <> 'SYNC' AND sl_node.no_id= ev_origin - ERROR: could not access file "$libdir/slony1_funcs.2.2.0.b1": No such file or directory error: unable to query event history on node 1 <stdin>:2: PGRES_FATAL_ERROR select "_test".getLocalNodeId('_test'); - ERROR: current transaction is aborted, commands ignored until end of transaction block <stdin>:2: database specified in ��V:1 reports no_id -1 If 2.2.0 b1 is no longer installed. I think this will effect any upgrade to 2.2.0 where the old shared library is not installed anymore. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 286] PG 9.3 has changed LookupExplicitNamespace to take two arguments
- Next message: [Slony1-bugs] [Bug 287] UPDATE FUNCTIONS in 2.2 doesn't work
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list