Re: Error-safe user functions

From: Joe Conway <mail(at)joeconway(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Error-safe user functions
Date: 2022-12-05 17:38:45
Message-ID: fda4baa5-8882-42ad-986e-4e6efe52211a@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/5/22 12:35, Robert Haas wrote:
> On Mon, Dec 5, 2022 at 12:27 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I wrote:
>> > Nah, it's so close to ereport that it looks like a typo. eseterr isn't
>> > awful, perhaps. Or maybe errXXXX, but I've not thought of suitable XXXX.
>>
>> ... "errsave", maybe?
>
> eseterr or errsave seem totally fine to me, FWIW.

+1

> I would probably choose a more verbose name if I were doing it, but I
> do get the point that keeping line lengths reasonable is important,
> and if someone were to accuse me of excessive prolixity, I would be
> unable to mount much of a defense.

prolixity -- nice word! I won't comment on its applicability to you in
particular ;-P

--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan Lemig 2022-12-05 17:39:01 Request to modify view_table_usage to include materialized views
Previous Message Robert Haas 2022-12-05 17:35:34 Re: Error-safe user functions