>> One thing we could think about if this seems too high is to drop
>> ROW_COUNT. I'm unconvinced that it has a real use-case, and it seems
>> to be taking more than its share of the work in non-error cases, because
>> it turns out that PQcmdTuples() is not an amazingly cheap function.
>
> I do think that a small overhead on a contrived case is worth removing the
> feature, as it is really insignificant on any realistic case.
Please read: I do NOT think that...
--
Fabien.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers