Tom Lane wrote:
Gary Horton [EMAIL PROTECTED] writes:
[ assorted startup problems ]
You did not say what platform this is on, nor which Postgres version
you are running. Tsk tsk.
Actually I did mention 7.3.4 Postgres but obviously I didn't do it
clearly. I really
Gary Horton [EMAIL PROTECTED] writes:
Tom Lane wrote:
The -w-doesn't-wait-long-enough bit needs investigation.
No messages, no smoking gun. If you mean running the sh script with -x,
it's really not complicated enough to warrant that - I've added echo
statements to confirm that it's just
Tom Lane wrote:
Yeah ... in fact, if you read the script, what it does is loop until a
psql -l succeeds ... so why wouldn't your following instance also
succeed?
regards, tom lane
Ah, I think that you mean to run pg_ctl with a -x option (not my own sh
script). I didn't realize I
I'm starting up postgresql with this command line:
/usr/bin/setpgrp ${POSTGRESQL_HOME}/bin/pg_ctl -w -o -i start
...and there are two things about this that raise a question. First, we
use the setpgrp because, although pg_ctl documentation (7.3.4) states
that it can be used for properly
Gary Horton [EMAIL PROTECTED] writes:
[ assorted startup problems ]
You did not say what platform this is on, nor which Postgres version
you are running. Tsk tsk.
As for the setpgrp business, that doesn't sound real unreasonable.
I use nohup for that purpose, and it seems to work fine on all
