Re: [patch] libpq one-row-at-a-time API

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Marko Kreen <markokr(at)gmail(dot)com>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [patch] libpq one-row-at-a-time API
Date: 2012-07-24 18:49:02
Message-ID: CAHyXU0wywwM0-fGj25=Wa47+dJ8qnS6Nv35jfENJ+SbMxMiGnA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 24, 2012 at 1:33 PM, Merlin Moncure <mmoncure(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2012-07-24 19:16:17 Re: [patch] libpq one-row-at-a-time API
Previous Message Merlin Moncure 2012-07-24 18:33:14 Re: [patch] libpq one-row-at-a-time API