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

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Robert Haas <robertmhaas@gmail.com>
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: Sun, 04 Dec 2022 10:25:23 -0500
Message-ID: <2629670.1670167523@sss.pgh.pa.us> (raw)
In-Reply-To: <ecaee1af-437b-9ef1-5140-9da0263f19b2@dunslane.net>
References: <3bbbb0df-7382-bf87-9737-340ba096e034@postgrespro.ru>
	<3190059.1665164276@sss.pgh.pa.us>
	<57b7cc2e-1215-3f43-84e4-6d9f8ad575df@dunslane.net>
	<CADkLM=djieyppZpKgveeDdt3QYLt+XQGHzpoa+Sd_Lwa5dDTWA@mail.gmail.com>
	<3049337.1669008405@sss.pgh.pa.us>
	<469338a3-da38-160f-23b9-813c261bc1d6@dunslane.net>
	<1677334.1669918475@sss.pgh.pa.us>
	<CA+TgmoY44nbY6Z7zbnQ1VwgDu79DbOHmh4o8K9cBu0OeC2Hndw@mail.gmail.com>
	<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>
	<ecaee1af-437b-9ef1-5140-9da0263f19b2@dunslane.net>

Andrew Dunstan <andrew@dunslane.net> writes:
> On 2022-12-03 Sa 16:46, Tom Lane wrote:
>> 1. Bikeshedding on my name choices is welcome.  I know Robert is
>> dissatisfied with "ereturn", but I'm content with that so I didn't
>> change it here.

> details_please seems more informal than our usual style. details_wanted
> maybe?

Yeah, Corey didn't like that either.  "details_wanted" works for me.

> Soon after we get this done I think we'll find we need to extend this to
> non-input functions. But that can wait a short while.

I'm curious to know exactly which other use-cases you foresee.
It wouldn't be a bad idea to write some draft code to verify
that this mechanism will work conveniently for them.

			regards, tom lane





view thread (175+ messages)  latest in thread

Message-ID: <2629670.1670167523@sss.pgh.pa.us>
Permalink:  ../2629670.1670167523@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2629670.1670167523@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, andrew@dunslane.net, robertmhaas@gmail.com, corey.huinker@gmail.com, n.gluhov@postgrespro.ru, pgsql-hackers@lists.postgresql.org
  Subject: Re: Error-safe user functions
  In-Reply-To: <2629670.1670167523@sss.pgh.pa.us>

* 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