Re: Error-safe user functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
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-01 20:49:42
Message-ID: 1703871.1669927782@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Dec 1, 2022 at 2:41 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'd be the first to agree that "ereturn"
>> doesn't capture that detail very well, but I don't have a better name.
>> (And I do like the fact that this name is the same length as "ereport",
>> so that we won't end up with lots of reindentation to do.)

> I don't think it's sensible to make decisions about important syntax
> on the basis of byte-length. Reindenting is a one-time effort; code
> clarity will be with us forever.

Sure, but without a proposal for a better name, that's irrelevant.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2022-12-01 21:12:25 Using WaitEventSet in the postmaster
Previous Message Andres Freund 2022-12-01 20:17:51 Re: meson PGXS compatibility