Re: Making psql error out on output failures

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: David Zhang <david(dot)zhang(at)highgo(dot)ca>
Cc: Daniel Verite <daniel(at)manitou-mail(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Making psql error out on output failures
Date: 2020-02-28 16:03:59
Message-ID: 20200228160359.GA32501@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-02-28 16:05:35 Re: Libpq support to connect to standby server as priority
Previous Message Alvaro Herrera 2020-02-28 15:57:09 Re: Created feature for to_date() conversion using patterns 'YYYY-WW', 'YYYY-WW-D', 'YYYY-MM-W' and 'YYYY-MM-W-D'