From: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> |
---|---|
To: | Sean Chittenden <sean(at)chittenden(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Joel Rees <joel(at)alpsgiken(dot)gr(dot)jp>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pgsql password when FreeBSD boots -- what's |
Date: | 2003-04-04 03:58:42 |
Message-ID: | 5.1.0.14.1.20030404115230.020ea600@mbox.jaring.my |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Actually the fact that a pg client finds it needs a password is usually
good enough.
e.g. if the client gets connected and can exit, assume db is up
if the client finds it needs a password to fully connect, assume db is up.
If there is no response, assume db is down.
Link.
At 12:52 PM 4/3/03 -0800, Sean Chittenden wrote:
>I've added the pg_ping util to my todo list, but I'm swamped atm. Are
>there any request bits that could be used for interactivity with the
>server beyond the server being able to accept a connection?
>
>-sc
>
>--
>Sean Chittenden
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
From | Date | Subject | |
---|---|---|---|
Next Message | Tamir Halperin | 2003-04-04 04:06:10 | Re: Rules, Triggers something more challenging |
Previous Message | Lonni Friedman | 2003-04-04 03:45:15 | Re: unable to dump database, toast errors |