Re: postgres startup script, long delay when auth = password

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dave" <dave(at)hawk-systems(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: postgres startup script, long delay when auth = password
Date: 2002-04-19 20:47:06
Message-ID: 3968.1019249226@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Dave" <dave(at)hawk-systems(dot)com> writes:
> Is it actually taking that long for the database to start? or is pg_ctl not
> picking up on whatever indicator it uses to determine that the database has
> indeed started?

The "indicator" is whether it can connect with psql or not;
unfortunately it is not bright enough to distinguish a password failure
from other failures. You might be entertained to read Peter E's
commentary near the bottom of pg_ctl (it's only a shell script,
feel free to take a look).

Perhaps pg_ctl could be enhanced to distinguish connection failures
(which is what it really cares about) from authorization failures.
Or maybe there's some other way that would address Peter's other gripes.
I have no time to think about it, but if anyone wants to work on it ...

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nigel J. Andrews 2002-04-19 21:11:19 ROWTYPE as parameter to function
Previous Message Dave 2002-04-19 20:41:34 postgres startup script, long delay when auth = password