Re: [patch] libpq one-row-at-a-time API - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: [patch] libpq one-row-at-a-time API
Date
Msg-id CAHyXU0wywwM0-fGj25=Wa47+dJ8qnS6Nv35jfENJ+SbMxMiGnA@mail.gmail.com
Whole thread Raw
In response to Re: [patch] libpq one-row-at-a-time API  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: [patch] libpq one-row-at-a-time API
List pgsql-hackers
On Tue, Jul 24, 2012 at 1:33 PM, Merlin Moncure <mmoncure@gmail.com> wrote:
> The 'source' result (or source data that would be copied into the
> destination result) would be stored in the PGconn, right? So, the idea
> is that when you set up single row mode the connection generates a
> template PGconn which is then copied out repeatedly during row-by-row
> processing.  I like it, but only if we're reasonably confident the
> PGresult can be sufficiently optimized like that.

hm, PGresAttDesc is unfortunately in the public header and as such
probably can't be changed?

merlin


pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: [patch] libpq one-row-at-a-time API
Next
From: Merlin Moncure
Date:
Subject: Re: [patch] libpq one-row-at-a-time API