Francois Suter <dba@paragraf.ch> writes:
> the following scenario: Postgres starts after quite a few other
> processes, tries to start with the pid stored in the postmaster.pid
> file and actually doesn't start because the pid is already in use.
Postgres does not "try to start with the stored pid"; that's entirely
impossible under any flavor of Unix. You get the PID the kernel assigns
you, and that's that. This could well be a problem of failure to start
up, but you're barking up the wrong tree as to why.
What is needed at this point is more observation. You need to determine
whether the postmaster is in fact starting (and later dying) or
failing to start at all --- ie, is the postmaster.pid file left over
from a previous system boot cycle? Checking the mod date of the pid
file might be enough to tell.
> Is there an error log somewhere where such an error might appear?
What are you doing with the postmaster's stderr? If your start script
for the postmaster is routing it to /dev/null, send it someplace more
helpful.
regards, tom lane