pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Joe Conway <mail@joeconway.com>
To: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Corey Huinker <corey.huinker@gmail.com>
Cc: Nikita Glukhov <n.gluhov@postgrespro.ru>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Error-safe user functions
Date: Mon, 5 Dec 2022 12:38:45 -0500
Message-ID: <fda4baa5-8882-42ad-986e-4e6efe52211a@joeconway.com> (raw)
In-Reply-To: <CA+TgmoZu_GQ43J073n4_+OFGV36oj=tMqR=gKbiPXbwy5k+=+Q@mail.gmail.com>
References: <3bbbb0df-7382-bf87-9737-340ba096e034@postgrespro.ru>
	<1695760.1669923671@sss.pgh.pa.us>
	<CA+TgmobpfOx0WT+ZG71eB5=JrKUi-VX7FwsVF6E8ps1WfKYYcQ@mail.gmail.com>
	<1703871.1669927782@sss.pgh.pa.us>
	<CA+TgmoaxLcxpLmFJ=QiOThfPRGLhRH+o2XZmVie2KOk5TKGbKg@mail.gmail.com>
	<1721519.1669934025@sss.pgh.pa.us>
	<CA+TgmoZ5tQz4sZfXOAK-wx7e2d2+pGg4EEc1TA4sb9gNMjm4Fw@mail.gmail.com>
	<1925585.1669990324@sss.pgh.pa.us>
	<02cf2f81-a776-37ff-291c-100480722a5c@dunslane.net>
	<2503569.1670104001@sss.pgh.pa.us>
	<CADkLM=end5RBrsQMfyB8VxvOmu5AZzsffQbDJge3TjtkxUGkEQ@mail.gmail.com>
	<CA+Tgmoa-A61npwUqzGs7J-tt6RaCwOx-p=cx+Xss=fyjeSTDew@mail.gmail.com>
	<3304244.1670256567@sss.pgh.pa.us>
	<CA+TgmoZHVbfhv2+9G=DDNAMDtjEFX3CF684Sw+8Dh95qtqudwg@mail.gmail.com>
	<befa11aa-9b99-35db-1166-94472e1cc946@dunslane.net>
	<3311570.1670260484@sss.pgh.pa.us>
	<3319836.1670261262@sss.pgh.pa.us>
	<CA+TgmoZu_GQ43J073n4_+OFGV36oj=tMqR=gKbiPXbwy5k+=+Q@mail.gmail.com>

On 12/5/22 12:35, Robert Haas wrote:
> On Mon, Dec 5, 2022 at 12:27 PM Tom Lane <tgl@sss.pgh.pa.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






view thread (175+ messages)  latest in thread

Message-ID: <fda4baa5-8882-42ad-986e-4e6efe52211a@joeconway.com>
Permalink:  ../fda4baa5-8882-42ad-986e-4e6efe52211a@joeconway.com/
Also on:    postgresql.org/message-id/fda4baa5-8882-42ad-986e-4e6efe52211a@joeconway.com

 · 

reply
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 using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: mail@joeconway.com, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, andrew@dunslane.net, corey.huinker@gmail.com, n.gluhov@postgrespro.ru, pgsql-hackers@lists.postgresql.org
  Subject: Re: Error-safe user functions
  In-Reply-To: <fda4baa5-8882-42ad-986e-4e6efe52211a@joeconway.com>

* 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