Shira Bezalel <shira@sfei.org> writes:
> The documentation states about the logging collector:
> "Note: It is possible to log to stderr without using the logging collector; the log messages will just go to wherever
theserver's stderr is directed. However, that method is only suitable for low log volumes, since it provides no
convenientway to rotate log files. Also, on some platforms not using the logging collector can result in lost or
garbledlog output, because multiple processes writing concurrently to the same log file can overwrite each other's
output."
> (From here: http://www.postgresql.org/docs/9.1/interactive/runtime-config-logging.html)
> By "multiple processes", does this refer to multiple postgresql servers running on the same machine?
No, it's referring to the fact that the server is made up of multiple
processes.
If you log to stderr without any collector, you almost certainly will
sometimes get garbled output (e.g. messages from different subprocesses
getting interleaved). IME this is not a big deal if you're only
occasionally inspecting the log by eyeball --- I generally run all
my development servers that way, and seldom see the problem. However,
if you're ever trying to machine-parse the logs, say with pgfouine,
even infrequent interleavings can be a problem.
regards, tom lane
