From: | James Coleman <jtc331(at)gmail(dot)com> |
---|---|
To: | andres(at)anarazel(dot)de |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Error handling expectations |
Date: | 2018-10-15 17:30:47 |
Message-ID: | CAAaqYe-uLOXiFVwafrB0m4ijhh_jm7ksYNi=KFA=aTTjeeWfsA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Perfect. Thanks for the pointer, Andres, that's exactly what I was looking
for.
On Mon, Oct 15, 2018 at 1:28 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On 2018-10-15 13:21:04 -0400, James Coleman wrote:
> > This my first real foray into the Postgres codebase, so an beginner
> > question: I noticed that existing C functions in pageinspect often do
> error
> > checking and then report the error with ereport but still continue on to
> > execute the rest of the function instead of early returning. Is this
> > standard practice? Or should I be reporting the error and then cleaning
> up
> > and returning rather than continuing to execute?
>
> ereport basically throws an exception when elevel >= ERROR. I suggest
> looking at elog.h's comments above elog and PG_TRY().
>
> Greetings,
>
> Andres Freund
>
From | Date | Subject | |
---|---|---|---|
Next Message | Corey Huinker | 2018-10-15 17:41:33 | Re: CopyFrom() has become way too complicated |
Previous Message | Andres Freund | 2018-10-15 17:28:26 | Re: Error handling expectations |