Re: ERROR: invalid memory alloc request size - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ERROR: invalid memory alloc request size
Date
Msg-id 18190.1130420154@sss.pgh.pa.us
Whole thread Raw
In response to Re: ERROR: invalid memory alloc request size  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: ERROR: invalid memory alloc request size
List pgsql-hackers
Martijn van Oosterhout <kleptog@svana.org> writes:
> Hmm, depends. It's not asked often, that for sure. Yet everytime it
> comes up I keep forgetting if I should be breaking on errstart, errmsg
> or something else. One of these days I might just write it on a post-it
> note next to my computer.

I always break on errfinish myself.  At one time elog didn't go through
errstart (it may still not, I forget) so errfinish was the only
certainly common point for catching both elog and ereport.  Another
advantage is that by that point, all the error info is set up and you
can inspect it if you want to.

> - Note that DEBUG level message will trigger
> - also so you might need to "cont" a few times to get the error you
> - want.

Also, control doesn't come to errfinish at all unless the message is
going to be printed, so the DEBUG-message problem goes away.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: localhost in pgpass file?
Next
From: Tom Lane
Date:
Subject: Re: ERROR: invalid memory alloc request size