Re: [PATCH] Provide rowcount for utility SELECTs - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] Provide rowcount for utility SELECTs
Date
Msg-id 11409.1262017219@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] Provide rowcount for utility SELECTs  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [PATCH] Provide rowcount for utility SELECTs  (Boszormenyi Zoltan <zb@cybertec.at>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On mån, 2009-12-28 at 11:08 -0500, Tom Lane wrote:
>> 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?

It's more the possibility of doing strcmp(tag, "SELECT") on the command
tag that worries me.  Describing the API change here as being limited
to PQcmdTuples misses the point rather completely: this is a protocol
change, and could break both clients and non-libpq driver libraries.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: updateMinRecoveryPoint bug?
Next
From: Bruce Momjian
Date:
Subject: Re: Removing pg_migrator limitations