| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Boszormenyi Zoltan <zb(at)cybertec(dot)at>, Hans-Juergen Schoenig <hs(at)cybertec(dot)at>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Provide rowcount for utility SELECTs |
| Date: | 2009-12-28 16:14:04 |
| Message-ID: | 1262016844.10841.1.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On mån, 2009-12-28 at 11:08 -0500, Tom Lane wrote:
> Boszormenyi Zoltan <zb(at)cybertec(dot)at> writes:
> > Hans-Juergen Schoenig írta:
> >> just as a background info: this will have some positive side effects
> >> on embedded C programs which should be portable.
>
> > Not just embedded C programs, every driver that's
> > based on libpq and used PQcmdTuples() will
> > automatically see the benefit.
>
> And, by the same token, the scope for possibly breaking clients is nearly
> unlimited ...
Why is that? Are there programs out there that expect PQcmdTuples() to
return something that is *not* the tuple count for these commands and
will violently misbehave otherwise?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-12-28 16:14:12 | Re: updateMinRecoveryPoint bug? |
| Previous Message | Tom Lane | 2009-12-28 16:08:19 | Re: [PATCH] Provide rowcount for utility SELECTs |