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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Corey Huinker <corey.huinker@gmail.com>

Cc: pgsql-hackers@lists.postgresql.org, Vik Fearing <vik@postgresfriends.org>

Date: 2023-01-03T18:14:05Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Make cast functions to type money error safe
- b36b95640487 19 (unreleased) landed
Make cast function from circle to polygon error safe
- 26f9012beecf 19 (unreleased) landed
Make geometry cast functions error safe
- 45cdaf3665be 19 (unreleased) landed
Make cast functions from jsonb error safe
- 10e4d8aaf46f 19 (unreleased) landed
Make many cast functions error safe
- e2f289e5b9b8 19 (unreleased) landed
Add SQL/JSON query functions
- 6185c9737cf4 17.0 cited
Add soft error handling to some expression nodes
- aaaf9449ec6b 17.0 cited

Corey Huinker <corey.huinker@gmail.com> writes:
> On Mon, Jan 2, 2023 at 10:57 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> While I approve of trying to get some functionality in this area,
>> I'm not sure that extending CAST is a great idea, because I'm afraid
>> that the SQL committee will do something that conflicts with it.

> I'm going off the spec that Vik presented in
> https://www.postgresql.org/message-id/f8600a3b-f697-2577-8fea-f40d3e18bea8@postgresfriends.org
> which is his effort to get it through the SQL committee.

I'm pretty certain that sending something to pgsql-hackers will have
exactly zero impact on the SQL committee.  Is there anything actually
submitted to the committee, and if so what's its status?

			regards, tom lane