Feature request: better debug messages
So, I've been trying to restore a PITR backup, and I've been having
problems. But by far the biggest problem I've been having is that
postgres doesn't give me *any* clue as to what I'm doing wrong. All
that happens is that pg_ctl will report 'postmaster starting', the log
file will say 'LOG: logger shutting down', and that's it. So I thought
upping the debug level of postgres would help, by adding a -o '-d 5' to
the pg_ctl command line. The log file that gets spit out in this case
is attached. What is noticeable is how unhelpfull it is.
So this is my request: When something happens to cause postgres to exit
early, have some sort of debug message giving some clue as to what is
wrong. For example 'parse error in recovery.conf' would be sufficient.
Thanks.
Brian
Attachments:
Brian Hurt wrote:
So I thought upping the debug level of postgres would help, by adding
a -o '-d 5' to the pg_ctl command line. The log file that gets spit
out in this case is attached. What is noticeable is how unhelpfull
it is.
I think this is just the stderr. The rest of the error messages are
going somewhere else -- syslog maybe?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
Alvaro Herrera <alvherre@commandprompt.com> writes:
Brian Hurt wrote:
So I thought upping the debug level of postgres would help, by adding
a -o '-d 5' to the pg_ctl command line. The log file that gets spit
out in this case is attached. What is noticeable is how unhelpfull
it is.
I think this is just the stderr. The rest of the error messages are
going somewhere else -- syslog maybe?
Since we see that the logger subprocess was running, presumably the
messages went wherever the logger has been told to put them. All that
you're going to see on stderr is messages that came out before the
logger got launched.
regards, tom lane