Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions - Mailing list pgsql-hackers

From Vik Fearing
Subject Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions
Date
Msg-id 4e00626a-66ca-45af-9866-30d022523b37@postgresfriends.org
Whole thread Raw
In response to Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions  (Corey Huinker <corey.huinker@gmail.com>)
List pgsql-hackers


On 31/03/2026 22:02, Corey Huinker wrote:


On Tue, Mar 31, 2026 at 10:48 AM jian he <jian.universality@gmail.com> wrote:
Hi.
I've incorporated the changes you sent me off-list.
The attached v1 no-cfbot is your proposed change.
I also did some minor comments adjustments.

The remaining patches continue to work for me. I hope we can get all of this into 19, but if we can't I think it would be ok to limit src/dest type combinations to those that can be handled by CoerceViaIO, at least for 19. I think the vast majority of the usage of this function will be mass ETLs where data is first loaded into a table of all text.


Did you see on Discord that I am submitting a bug fix for this paper? I originally took the syntax from json but it special-cases NULL and can't handle <empty specification>, so I want to remove `NULL ON CONVERSION ERROR` and switch the DEFAULT clause to <implicitly typed value specification>.


I am attaching it here in case you missed it.

-- 

Vik Fearing

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 9.0px Courier; color: #00

Attachment

pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: vectorized CRC on ARM64
Next
From: Ashutosh Bapat
Date:
Subject: Re: Shared hash table allocations