Re: error handling in pqRowProcessor broken - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: error handling in pqRowProcessor broken
Date
Msg-id e4bd5c16-be26-750c-e68a-701905eaf160@enterprisedb.com
Whole thread Raw
In response to Re: error handling in pqRowProcessor broken  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: error handling in pqRowProcessor broken
List pgsql-hackers
On 19.04.22 21:16, Tom Lane wrote:
> Peter Eisentraut<peter.eisentraut@enterprisedb.com>  writes:
>> I find that this doesn't work anymore.  If you set *errmsgp = "some
>> message" and return 0, then psql will just print a result set with zero
>> rows.
> Ah, I see the problem: a few places in fe-protocol3 didn't get the memo
> that conn->error_result represents a "pending" PGresult that hasn't
> been constructed yet.  The attached fixes it for me --- can you try it
> on whatever test case led you to this?

Your patch fixes it for me.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Add --{no-,}bypassrls flags to createuser
Next
From: "David G. Johnston"
Date:
Subject: Re: Add --{no-,}bypassrls flags to createuser