Stephen Frost <sfrost@snowman.net> writes:
> I can see how having a callback would be useful though I think for a
> good number of cases it's just going to be populating a memory region
> with it and we could cover that common case by providing an API for
> exactly that.
We already have that: it's called the existing libpq API.
The only reason I can see for offering any new feature in this area is
to cater to apps that want to transform the data representation
on-the-fly, not merely dump it into an area that will be the functional
equivalent of a PGresult. So it really has to be a callback.
> The other issue with a callback is that libpq would have
> to either call the callback for each value (not my preference)
Why not? That would eliminate a number of problems.
regards, tom lane