Re: Bug? 'psql -l' in pg_ctl?

From: Larry Rosenman <ler(at)lerctr(dot)org>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Bug? 'psql -l' in pg_ctl?
Date: 2000-11-30 02:26:00
Message-ID: 20001129202600.A8885@lerami.lerctr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [001129 20:22]:
> > 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.
>
> I fixed that today; if the database status is not open-for-business,
> the postmaster will tell you so right away instead of making you go
> through the authentication protocol first. So a pg_ping could be
> written that just sends a connection request packet and sees what
> comes back.
>
> However, if we're running in TRUST or IDENT mode, it's possible that
> that technique will lead to launching a backend to no purpose. So
> maybe we ought to extend the postmaster protocol to have a "query
> status" packet type. Thoughts?
I'd also like to see a protocol extension or some such to maybe
collect SNMP or other statistical data that could be used later for
tuning. If we do a protocol change, let's make it extensible....

LER

>
> regards, tom lane
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2000-11-30 03:00:38 Re: Trigger firing order
Previous Message Tom Lane 2000-11-30 02:20:11 Re: Bug? 'psql -l' in pg_ctl?