| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: error handling in pqRowProcessor broken |
| Date: | 2022-04-19 14:54:30 |
| Message-ID: | 2551224.1650380070@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-04-19 15:26:45 | Re: pg14 psql broke \d datname.nspname.relname |
| Previous Message | Peter Eisentraut | 2022-04-19 14:53:45 | Re: automatically generating node support functions |