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

From David Zhang
Subject Re: Making psql error out on output failures
Date
Msg-id dc985d99-4ad5-08de-4da6-136e17439ae3@highgo.ca
Whole thread Raw
In response to Re: Making psql error out on output failures  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Making psql error out on output failures
List pgsql-hackers
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

Attachment

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions
Next
From: Andres Freund
Date:
Subject: Catalog invalidations vs catalog scans vs ScanPgRelation()