Re: Concurrent psql patch - Mailing list pgsql-patches

From Andrew Dunstan
Subject Re: Concurrent psql patch
Date
Msg-id 4655F1C0.7040408@dunslane.net
Whole thread Raw
In response to Re: Concurrent psql patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Concurrent psql patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>
>> If we're going to include libpq-int.h maybe we need to put it in
>> common.h. Is there a reason that our own client programs shouldn't use
>> our own library internals?
>>
>
> Seems like a really bad idea to me.  I know I've cursed mysql more than
> once for doing the equivalent.  Also, if psql needs more than is
> currently exported as official API, why wouldn't other programs need it
> too?  If there's more needed here, let's see an official API change,
> not a hack.
>
>
>

Well, I guess the obvious API would be something like:

    PGAsyncStatusType PQasyncStatus(const PGconn *conn);

cheers

andrew

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Concurrent psql patch
Next
From: Tom Lane
Date:
Subject: Re: Concurrent psql patch