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

From Tom Lane
Subject Re: error handling in pqRowProcessor broken
Date
Msg-id 2551224.1650380070@sss.pgh.pa.us
Whole thread Raw
In response to error handling in pqRowProcessor broken  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> The error handling for pqRowProcessor is described as
>   *    Add the received row to the current async result (conn->result).
>   *    Returns 1 if OK, 0 if error occurred.
>   *
>   * On error, *errmsgp can be set to an error string to be returned.
>   * If it is left NULL, the error is presumed to be "out of memory".

> I find that this doesn't work anymore.

Will look into it, thanks for reporting.

(Hmm, seems like this API spec is deficient anyway.  Is the error
string to be freed later?  Is it already translated?)

            regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: automatically generating node support functions
Next
From: Tom Lane
Date:
Subject: Re: pg14 psql broke \d datname.nspname.relname