Re: Error-safe user functions

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-11-21 05:17:12
Message-ID: CADkLM=djieyppZpKgveeDdt3QYLt+XQGHzpoa+Sd_Lwa5dDTWA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 15, 2022 at 11:36 AM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:

>
> On 2022-10-07 Fr 13:37, Tom Lane wrote:
>
>
> [ lots of detailed review ]
>
> > Basically, this patch set should be a lot smaller and not have ambitions
> > beyond "get the API right" and "make one or two datatypes support COPY
> > NULL_ON_ERROR". Add more code once that core functionality gets reviewed
> > and committed.
> >
> >
>
>
> Nikita,
>
> just checking in, are you making progress on this? I think we really
> need to get this reviewed and committed ASAP if we are to have a chance
> to get the SQL/JSON stuff reworked to use it in time for release 16.
>
>
I'm making an attempt at this or something very similar to it. I don't yet
have a patch ready.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-11-21 05:26:45 Re: Error-safe user functions
Previous Message Corey Huinker 2022-11-21 05:09:08 Re: Multitable insert syntax support on Postgres?