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

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql - add special variable to reflect the last query status
Date: 2017-09-13 09:27:16
Message-ID: alpine.DEB.2.20.1709131126390.20876@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-09-13 09:28:28 Re: increasing the default WAL segment size
Previous Message Thomas Munro 2017-09-13 09:27:06 Re: Getting error message with latest PG source on Windows.