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>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Amul Sul <sulamul(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Alexander Korotkov <aekorotkov(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-26 19:12:06
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2022-12-26 Mo 12:47, Tom Lane wrote:
> Here's a proposed patch for making tsvectorin and tsqueryin
> report errors softly. We have to take the changes down a
> couple of levels of subroutines, but it's not hugely difficult.


> With the other patches I've posted recently, this covers all
> of the core datatype input functions. There are still half
> a dozen to tackle in contrib.

Yeah, I'm currently looking at those in ltree.



Andrew Dunstan

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Nikita Malakhov 2022-12-26 19:15:05 Passing relation metadata to Exec routine
Previous Message Ranier Vilela 2022-12-26 18:53:55 Re: ARRNELEMS Out-of-bounds possible errors