Re: Making psql error out on output failures - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Making psql error out on output failures
Date
Msg-id 20200228160359.GA32501@alvherre.pgsql
Whole thread Raw
In response to Re: Making psql error out on output failures  (David Zhang <david.zhang@highgo.ca>)
Responses Re: Making psql error out on output failures
List pgsql-hackers
On 2020-Feb-18, David Zhang wrote:

> 3. I think a better way to resolve this issue will still be the solution
> with an extra %m, which can make the error message much more informative to
> the end users.

Yes, agreed.  However, we use a style like this:

        pg_log_error("could not print tuples: %m");

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Created feature for to_date() conversion using patterns'YYYY-WW', 'YYYY-WW-D', 'YYYY-MM-W' and 'YYYY-MM-W-D'
Next
From: Alvaro Herrera
Date:
Subject: Re: Libpq support to connect to standby server as priority