| From: | Marko Kreen <markokr(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Postgres Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: [patch] libpq one-row-at-a-time API |
| Date: | 2012-07-24 16:57:09 |
| Message-ID: | CACMqXCJzumEdF78+itFcp_u0_Q_0h+2OWzkkqNyG6t7qk+B7Mw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 24, 2012 at 7:52 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> But, the faster rowbuf method is a generally incompatible way of
> dealing with data vs current libpq -- this is bad. If it's truly
> impossible to get those benefits without bypassing result API that
> then I remove my objection on the grounds it's optional behavior (my
> gut tells me it is possible though).
Um, please clarify what are you talking about here?
What is the incompatibility of PGresult from branch 1?
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-07-24 16:59:13 | Re: [patch] libpq one-row-at-a-time API |
| Previous Message | Merlin Moncure | 2012-07-24 16:52:10 | Re: [patch] libpq one-row-at-a-time API |