From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions |
Date: | 2023-01-03 18:32:58 |
Message-ID: | e2b31d7f-e44c-62a3-4469-0065d5e7fbf6@postgresfriends.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1/3/23 19:14, Tom Lane wrote:
> Corey Huinker <corey(dot)huinker(at)gmail(dot)com> writes:
>> On Mon, Jan 2, 2023 at 10:57 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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?
I have not posted my paper to the committee yet, but I plan to do so
before the working group's meeting early February. Just like with
posting patches here, I cannot guarantee that it will get accepted but I
will be arguing for it.
I don't think we should add that syntax until I do get it through the
committee, just in case they change something.
--
Vik Fearing
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2023-01-03 18:33:24 | Re: Simplify standby state machine a bit in WaitForWALToBecomeAvailable() |
Previous Message | Nathan Bossart | 2023-01-03 18:21:55 | Re: wake up logical workers after ALTER SUBSCRIPTION |