Skip site navigation (1) Skip section navigation (2)

Re: Concurrent psql patch

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, David Fetter <david(at)fetter(dot)org>, Jim Nasby <decibel(at)decibel(dot)org>, pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Concurrent psql patch
Date: 2007-05-24 20:12:48
Message-ID: 4655F1C0.7040408@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-05-24 20:16:26
Subject: Re: Concurrent psql patch
Previous:From: Tom LaneDate: 2007-05-24 20:07:27
Subject: Re: Prepare/Declare

pgsql-patches by date

Next:From: Tom LaneDate: 2007-05-24 20:16:26
Subject: Re: Concurrent psql patch
Previous:From: Tom LaneDate: 2007-05-24 19:04:34
Subject: Re: Concurrent psql patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group