Re: psql - add special variable to reflect the last query status
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Pavel Stehule <pavel.stehule@gmail.com>,
PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2017-09-05T18:08:11Z
Lists: pgsql-hackers
Fabien COELHO <coelho@cri.ensmp.fr> writes: >> * It might be better if SQLSTATE and ERROR_MESSAGE were left >> unchanged by a non-error query. > Hmmm. I'm not sure. If so, ERROR_MESSAGE should be LAST_ERROR_MESSAGE > maybe? Then what about LAST_ERROR_SQLSTATE to go with it, and let SQLSTATE > & ERROR_MESSAGE reflect the last command, and ERROR is just the boolean to > test if it occured? >> That would reduce the need to copy them into other variables just >> because you needed to do something else before printing them. It'd save >> a few cycles too. > Well, my suggestion would mean that they would be copied when an error > occurs, but only when it occurs, which would not be often. Uh ... what? regards, tom lane
Commits
-
Add psql variables to track success/failure of SQL queries.
- 69835bc89888 11.0 landed