From: | "Chad R(dot) Larson" <clarson(at)eldocomp(dot)com> |
---|---|
To: | "Matthew D(dot) Fuller" <fullermd(at)over-yonder(dot)net>, Dave <dave(at)hawk-systems(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgres not starting at boot(FreeBSD) - startup |
Date: | 2002-03-11 18:16:57 |
Message-ID: | 4.2.2.20020311111033.00c2f798@ecint.ecinet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
At 02:54 AM 3/11/2002 , Matthew D. Fuller wrote:
>It could also be said that having -w implemented as invoking psql to try
>to connect as the DB superuser assuming no password is a rather
>inappropriate way of going about it, but that's another can of worms.
It doesn't wait for the PID file to be created (at least, no on our 7.1.2
systems). It attempts to connect to a database using psql, and loops until
that connection is successful. Which it won't be if you've got a
password, because the script will wait for some entity to type the
password, and hang.
My fix here was a hack in pg_ctl, right at the bottom where the script is
looping on a psql attempt to connect to a database to prove the system is
up. I added a "-h localhost" to the psql invocation to force a TCP
connection, and then used "ident" instead of password for the authorization.
-crl
--
Chad R. Larson (CRL22) chad(at)eldocomp(dot)com
Eldorado Computing, Inc. 602-604-3100
5353 North 16th Street, Suite 400
Phoenix, Arizona 85016-3228
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-03-11 19:00:19 | Re: OIDs / noOIDs tables? |
Previous Message | Stephan Szabo | 2002-03-11 17:04:36 | Re: One sequence for different tables |
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Langille | 2002-03-11 18:49:51 | using syslog to capture RAISE notices |
Previous Message | Eric Webber | 2002-03-11 18:06:54 | Re: [lxp-general] Re: FREE ERD TOOL for POSTGRES ??? |