pgsql: Make the numeric-OID cases of regprocin and friends be non-throw

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Make the numeric-OID cases of regprocin and friends be non-throw
Date: 2022-12-24 20:01:29
Message-ID: E1p9Ai1-000DcQ-4U@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2022-12-24 20:22:00 pgsql: Convert jsonpath's input function to report errors softly
Previous Message David Rowley 2022-12-24 00:19:47 pgsql: Fix recent accidental omission in pg_proc.dat