| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Error-safe user functions |
| Date: | 2022-11-15 16:35:55 |
| Message-ID: | 57b7cc2e-1215-3f43-84e4-6d9f8ad575df@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-11-15 16:36:21 | Re: HOT chain validation in verify_heapam() |
| Previous Message | Peter Eisentraut | 2022-11-15 16:07:05 | Re: meson oddities |