From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | grasshacker(at)over-yonder(dot)net, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Bug? 'psql -l' in pg_ctl? |
Date: | 2000-11-29 06:34:20 |
Message-ID: | 26668.975479660@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
>> Trying to connect does seem to be the most reliable way to verify
>> that the postmaster is open for business.
> Agreed.
> Do you think it's a good idea to invent a new command such as
> "pg_ping" or should we add a new option to psql instead?
I'd lean towards a pg_ping (Peter E., any comment here?)
Really we'd need to change the postmaster too, because what we need to
do is send a query "are you ready to accept connections?" that the
postmaster will answer without an authentication exchange. AFAIR this
is *not* immediately evident from the postmaster's current behavior ---
I think it will challenge you for a password even before the startup
subprocess is done.
Or we could invent a status file in $PGDATA that's separate from the
pid interlock file, and have pg_ctl look for that. But I think a
communication protocol might be cleaner.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | GH | 2000-11-29 08:42:52 | Re: Access restriction |
Previous Message | Tatsuo Ishii | 2000-11-29 06:15:46 | Re: Bug? 'psql -l' in pg_ctl? |