From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Make the numeric-OID cases of regprocin and friends be non-throw
Date: Sat, 24 Dec 2022 20:01:29 +0000
Message-ID: <E1p9Ai1-000DcQ-4U@gemulon.postgresql.org> (raw)
Make the numeric-OID cases of regprocin and friends be non-throwing.
While at it, use a common subroutine already.
This doesn't move the needle very far in terms of making these
functions non-throwing; the only case we're now able to trap is
numeric-OID-is-out-of-range. Still, it seems like a pretty
non-controversial step in that direction.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/780ec9f1b2a44c118d1246325404ad0ed2226cbf
Modified Files
--------------
src/backend/utils/adt/regproc.c | 216 ++++++++++++++--------------------------
1 file changed, 77 insertions(+), 139 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us
Subject: Re: pgsql: Make the numeric-OID cases of regprocin and friends be non-throw
In-Reply-To: <E1p9Ai1-000DcQ-4U@gemulon.postgresql.org>
References: <E1p9Ai1-000DcQ-4U@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox