| commit | 9520f8d92a8681e441cc863422babd544353dd39 | |
| author | Peter Eisentraut <peter@eisentraut.org> | |
| Mon, 23 May 2022 08:07:36 +0000 (23 10:07 +0200) | ||
| committer | Peter Eisentraut <peter@eisentraut.org> | |
| Mon, 23 May 2022 08:07:36 +0000 (23 10:07 +0200) | ||
| tree | 4093f42133d2c4cc17b6042c855f99fecb193850 | treesnapshot (tar.gz zip) |
| parent | 6e647ef0e750bc5007e4af48b19023d68ae91b6a | commitdiff |
psql: Update \timing also in case of an error
The changes to show all query results (7844c9918) broke \timing output
in case of an error; it didn't update the timing result and showed
0.000 ms.
Fix by updating the timing result also in the error case. Also, for
robustness, update the timing result any time a result is obtained,
not only for the last, so a sensible value is always available.
Reported-by: Tom Lane <tgl@sss.pgh.pa.us>
Author: Richard Guo <guofenglinux@gmail.com>
Author: Fabien COELHO <coelho@cri.ensmp.fr>
Discussion: https://www.postgresql.org/message-id/3813350.1652111765%40sss.pgh.pa.us
The changes to show all query results (7844c9918) broke \timing output
in case of an error; it didn't update the timing result and showed
0.000 ms.
Fix by updating the timing result also in the error case. Also, for
robustness, update the timing result any time a result is obtained,
not only for the last, so a sensible value is always available.
Reported-by: Tom Lane <tgl@sss.pgh.pa.us>
Author: Richard Guo <guofenglinux@gmail.com>
Author: Fabien COELHO <coelho@cri.ensmp.fr>
Discussion: https://www.postgresql.org/message-id/3813350.1652111765%40sss.pgh.pa.us
| src/bin/psql/common.c | diffblobblamehistory | |
| src/bin/psql/t/001_basic.pl | diffblobblamehistory |