Re: PG_RE_THROW is mandatory (was Re: jsonpath) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG_RE_THROW is mandatory (was Re: jsonpath)
Date
Msg-id 24548.1549570108@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG_RE_THROW is mandatory (was Re: jsonpath)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: PG_RE_THROW is mandatory (was Re: jsonpath)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> So,

> "The error recovery code can either do PG_RE_THROW to propagate the
> error outwards, or do a (sub)transaction abort.  Failure to do so may
> leave the system in an inconsistent state for further processing."

WFM.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: PG_RE_THROW is mandatory (was Re: jsonpath)
Next
From: Daniel Gustafsson
Date:
Subject: Re: Tighten up a few overly lax regexes in pg_dump's tap tests