Fri Apr 22 16:33:08 PDT 2005
- Previous message: [Slony1-commit] By cbbrowne: Added a "best practices" document (not yet complete, but
- Next message: [Slony1-commit] By wieck: LogTrigger should never be called in anything other than a
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message: ----------- LogTrigger should never be called in anything other than a client transaction on the origin. It's not defined on subscribers and slon should never UPDATE an origin. Jan Tags: ---- REL_1_0_STABLE Modified Files: -------------- slony1-engine/src/backend: slony1_funcs.c (r1.17.2.5 -> r1.17.2.6) -------------- next part -------------- Index: slony1_funcs.c =================================================================== RCS file: /usr/local/cvsroot/slony1/slony1-engine/src/backend/slony1_funcs.c,v retrieving revision 1.17.2.5 retrieving revision 1.17.2.6 diff -Lsrc/backend/slony1_funcs.c -Lsrc/backend/slony1_funcs.c -u -w -r1.17.2.5 -r1.17.2.6 --- src/backend/slony1_funcs.c +++ src/backend/slony1_funcs.c @@ -430,9 +430,8 @@ case SLON_ROLE_NORMAL: /* Normal, that's good */ break; - case SLON_ROLE_SLON: /* Replication session, nothing to do here */ - SPI_finish(); - return PointerGetDatum(NULL); + case default: /* non-client session ??? */ + elog(ERROR, "Slony-I: logTrigger() called in non-client session"); } /*
- Previous message: [Slony1-commit] By cbbrowne: Added a "best practices" document (not yet complete, but
- Next message: [Slony1-commit] By wieck: LogTrigger should never be called in anything other than a
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list