Re: Error-safe user functions

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Joe Conway <mail(at)joeconway(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-09 13:06:58
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2022-12-08 Th 21:59, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> On 2022-12-08 17:57:09 -0500, Tom Lane wrote:
>>> Given that this additional experimentation didn't find any holes
>>> in the API design, I think this is pretty much ready to go.
>> One interesting area is timestamp / datetime related code. There's been some
>> past efforts in the area, mostly in 5bc450629b3. See the RETURN_ERROR macro in
>> formatting.c.
>> This is not directly about type input functions, but it looks to me that the
>> functionality in the patchset should work.
> Yeah, I was planning to take a look at that before walking away from
> this stuff. (I'm sure not volunteering to convert ALL the input
> functions, but I'll do the datetime code.)

Awesome. Perhaps if there are no more comments you can commit what you
currently have so people can start work on other input functions.

Thanks for your work on this.



Andrew Dunstan

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2022-12-09 13:32:50 Re: [PoC] Improve dead tuple storage for lazy vacuum
Previous Message Jim Jones 2022-12-09 12:55:25 Authentication fails for md5 connections if ~/.postgresql/postgresql.{crt and key} exist