| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: psql: Catch and report errors while printing result table |
| Date: | 2020-03-20 15:13:45 |
| Message-ID: | E1jFJLF-0008WH-FZ@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
psql: Catch and report errors while printing result table
Errors (for example I/O errors or disk full) while printing out result
tables were completely ignored, which could result in silently
truncated output in scripts, for example. Fix by adding some basic
error checking and reporting.
Author: Daniel Verite <daniel(at)manitou-mail(dot)org>
Author: David Zhang <david(dot)zhang(at)highgo(dot)ca>
Discussion: https://www.postgresql.org/message-id/flat/9a0b3c8d-ee14-4b1d-9d0a-2c993bdabacc(at)manitou-mail(dot)org
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/b03436994bcc4909dd644fd5ae6d9a9acdf30da5
Modified Files
--------------
src/bin/psql/common.c | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2020-03-20 18:07:35 | pgsql: Turn off deprecated bison warnings under MSVC |
| Previous Message | Amit Kapila | 2020-03-20 03:02:31 | pgsql: Allow relation extension lock to conflict among parallel group m |