Re: Out-of-memory error reports in libpq - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Out-of-memory error reports in libpq
Date
Msg-id 6daed78d-8d45-acf4-fef6-9d73b572f863@dunslane.net
Whole thread Raw
In response to Re: Out-of-memory error reports in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Out-of-memory error reports in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 7/28/21 11:02 AM, Tom Lane wrote:
>
> Here I've got to disagree.  We do need the form with a PQExpBuffer
> argument, because there are some places where that isn't a pointer
> to a PGconn's errorMessage.  But the large majority of the calls
> are "pqReportOOM(conn)", and I think having to write that as
> "pqReportOOM(&conn->errorMessage)" is fairly ugly and perhaps
> error-prone.
>
> I'm not wedded to the name "pqReportOOMBuffer" though --- maybe
> there's some better name for that one?
>
>             



Is it worth making the first one a macro?


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: truncating timestamps on arbitrary intervals
Next
From: Robert Haas
Date:
Subject: Re: Have I found an interval arithmetic bug?