Re: Making psql error out on output failures

Hi Alvaro,

Thanks for your review, now the new patch with the error message in PG 
style is attached.

On 2020-02-28 8:03 a.m., Alvaro Herrera wrote:
> 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");
>
-- 
David

Software Engineer
Highgo Software Inc. (Canada)
www.highgo.ca