Wed May 16 11:35:14 PDT 2007
- Previous message: [Slony1-general] Slony Replication Slow
- Next message: [Slony1-general] Slony Replication Slow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Saw this in logs today coming from a cluster running slony-1.2.9 against
pg-8.2.4:
2007-05-16 13:29:08 CDT DEBUG1 cleanupThread: 0.203 seconds for delete logs
NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=7035
CONTEXT: SQL statement "SELECT "_ar_primary".cleanupNodelock()"
PL/pgSQL function "cleanupevent" line 77 at perform
NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=7035
CONTEXT: SQL statement "SELECT "_ar_primary".cleanupNodelock()"
PL/pgSQL function "cleanupevent" line 77 at perform
2007-05-16 13:30:35 CDT DEBUG1 cleanupThread: 0.019 seconds for
cleanupEvent()
2007-05-16 13:30:35 CDT DEBUG1 cleanupThread: 0.017 seconds for delete
logs
WARNING: nonstandard use of \\ in a string literal at character 99
HINT: Use the escape string syntax for backslashes, e.g., E'\\'.
WARNING: nonstandard use of \\ in a string literal at character 1251
HINT: Use the escape string syntax for backslashes, e.g., E'\\'.
Everything appears to be working correctly, but wasn't sure if this was an
'expected' message to see in log file.
-jason
- Previous message: [Slony1-general] Slony Replication Slow
- Next message: [Slony1-general] Slony Replication Slow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list