Re: libpq object hooks (libpq events) - Mailing list pgsql-hackers

From Andrew Chernow
Subject Re: libpq object hooks (libpq events)
Date
Msg-id 48BEC5DB.7000601@esilo.com
Whole thread Raw
In response to Re: libpq object hooks (libpq events)  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera wrote:
> Andrew Chernow escribió:
>> Alvaro Herrera wrote:
> 
>>> (I also removed PQresultAlloc.)
>> Nooooooo ... removing PQresultAlloc breaks libpqtypes!  It also removes 
>> some of the use cases provided by PQsetvalue, which allows one to add to 
>> a result (in our case from scratch).
> 
> I don't really see the point -- it's the same as pqResultAlloc, except
> that you have to pass an extra argument.  There's no actual
> functionality loss.
> 

libpqtypes uses it.  libpqtypes doesn't have access to any internals of 
libpq, including pqResultAlloc.  So, I made a public wrapper to the 
internal version.  The point is to provide public access to the result 
allocator.

-- 
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/


pgsql-hackers by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: [PATCH] Cleanup of GUC units code
Next
From: Tom Lane
Date:
Subject: Re: Function call order dependency