Re: Making psql error out on output failures

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Daniel Verite <daniel(at)manitou-mail(dot)org>, David Zhang <david(dot)zhang(at)highgo(dot)ca>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Making psql error out on output failures
Date: 2020-03-20 15:14:16
Message-ID: 0538955a-96cf-76a2-61d7-ca6bd37c8674@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-03-06 10:36, Daniel Verite wrote:
> David Zhang wrote:
>
>> Thanks for your review, now the new patch with the error message in PG
>> style is attached.
>
> The current status of the patch is "Needs review" at
> https://commitfest.postgresql.org/27/2400/
>
> If there's no more review to do, would you consider moving it to
> Ready for Committer?

committed

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2020-03-20 15:24:39 where EXEC_BACKEND is defined
Previous Message Justin Pryzby 2020-03-20 14:53:59 Re: error context for vacuum to include block number