Horton

Re: psql - add special variable to reflect the last query status

Fabien COELHO <coelho@cri.ensmp.fr>

View thread View on postgr.es
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Pavel Stehule <pavel.stehule@gmail.com>, PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2017-09-13T09:27:16Z
Lists: pgsql-hackers 
>> 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.

Commits

  1. Add psql variables to track success/failure of SQL queries.