On Fri, Jan 27, 2012 at 2:57 AM, Kyotaro HORIGUCHI
> Hello, This is a new version of the patch formerly known as
> 'alternative storage for libpq'.
I took a quick look at the patch and the docs. Looks good and agree
with rationale and implementation. I see you covered the pqsetvalue
case which is nice. I expect libpq C api clients coded for
performance will immediately gravitate to this api.
> - The meaning of PGresAttValue is changed. The field 'value' now
> contains a value withOUT terminating zero. This change seems to
> have no effect on any other portion within the whole source
> tree of postgresql from what I've seen.
This is a minor point of concern. This function was exposed to
support libpqtypes (which your stuff compliments very nicely by the
way) and I quickly confirmed removal of the null terminator didn't
cause any problems there. I doubt anyone else is inspecting the
structure directly (also searched the archives and didn't find
This needs to be advertised very loudly in the docs -- I understand
why this was done but it's a pretty big change in the way the api
In response to
pgsql-hackers by date
|Next:||From: Marko Kreen||Date: 2012-01-27 15:42:14|
|Subject: Re: Speed dblink using alternate libpq tuple storage|
|Previous:||From: Marti Raudsepp||Date: 2012-01-27 14:53:09|
|Subject: Re: Caching for stable expressions with constant arguments v6|