me> I'll put further thought into dblink-plus taking it into
me> Please let me have a little more time.
I've inquired the developer of dblink-plus about
RegisterResourceReleaseCallback(). He said that the function is
in bad compatibility with current implementation. In addition to
this, storing into tuplestore directly seems to me a good idea
than palloc'ed PGresult.
So I tried to make libpq/PGresult be able to handle alternative
tuple store by hinting to PGconn, and modify dblink to use the
mechanism as the first sample code.
I will show it as a series of patches in next message.
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Kyotaro HORIGUCHI||Date: 2011-12-01 10:24:19|
|Subject: Re: Allow substitute allocators for PGresult.|
|Previous:||From: jesper||Date: 2011-12-01 09:12:53|
|Subject: Re: Accounting for toast in query planner. (gin/gist