Tue Mar 21 08:17:36 PST 2006
- Previous message: [Slony1-general] Failover Failing for sub slaves
- Next message: [Slony1-general] Documentaion error for debug levle of slon command
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The documentation for the debug option of the slon command is
misleading, or else there is a glitch in the code.
Per the documenation:
Options
-ddebuglevel
The log_level specifies the level of verbosity that slon should use
when logging its activity.
The eight levels of logging are:
Error
Warn
Config
Info
Debug1
Debug2
Debug3
Debug4
However, if you try to specify a level of Error, Warn, Config or Info,
it is not accepted as the 1st line of the log file is
slon -dW -pslon_node_1.pid $USCUSTREP "dbname=$MASTERDBNAME
user=$REPLICATIONUSER host=$MASTERHOST port=$PGPORT" > slon1.log &
2006-03-21 11:01:01 MST WARN parameter "log_level" requires a integer
value
Trying to specify a different level of debug will report an error also
slon -d5 -pslon_node_1.pid $USCUSTREP "dbname=$MASTERDBNAME
user=$REPLICATIONUSER host=$MASTERHOST port=$PGPORT" > slon1.log &
2006-03-21 10:58:26 MST WARN 5 is outside the valid range for
parameter "log_level" (0 .. 4)
So it looks like the documentation should be corrected to read as follows:
The eight levels of logging are:
1 = Debug1 (Info)
2 = Debug2 (Config)
3.= Debug3 (Warn)
4 = Debug4 (Error)
Can someone please verify this for me?
TIA
--
Melvin Davidson
CCT - Database Developer
303-798-9228 ext. 305
- Previous message: [Slony1-general] Failover Failing for sub slaves
- Next message: [Slony1-general] Documentaion error for debug levle of slon command
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list