MIME-Version: 1.0
References: 
 <CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mDHcY4_qQ0+noCUVg@mail.gmail.com>
 <66e47fc0-77b7-4763-9b70-5c0b7ff15f21@eisentraut.org>
 <a2ee0c1a-5ef0-43ab-897c-b56adb25b34f@illuminatedcomputing.com>
 <333d3886-b737-45c3-93f4-594c96bb405d@eisentraut.org>
 <e8e51e74-10d7-410d-a1d1-8ec681d8436a@eisentraut.org>
 <f4056005-0fb7-417a-bcb3-e704f9aeadc3@illuminatedcomputing.com>
 <6a2247d9-461d-4b0a-b692-f0f3c0fab27f@eisentraut.org>
 <8f995a4c-64e3-40cd-bfed-06b54a280d36@illuminatedcomputing.com>
 <0832f18d-523f-4c15-acb0-338a785150c5@illuminatedcomputing.com>
 <5f0c25de-2c13-4fb5-a4df-a1e03c43cd14@illuminatedcomputing.com>
 <1b45f81d-4e99-4813-a2c6-72bf5fd80980@eisentraut.org>
 <e773bc11-4ac1-40de-bb91-814e02f05b6d@eisentraut.org>
 <3e061027-781d-42c1-b6e8-bafbf3b51033@eisentraut.org>
 <c3af7816-1944-4030-ab73-5b055de8cba3@illuminatedcomputing.com>
 <3b33690e-0d67-47a5-8424-93ac1fed4c26@eisentraut.org>
 <1085d8a3-17a7-4639-afd2-bd6dfa09713d@illuminatedcomputing.com>
 <6ac43c8e-5595-40d9-a039-ede12e7487e1@eisentraut.org>
In-Reply-To: <6ac43c8e-5595-40d9-a039-ede12e7487e1@eisentraut.org>
From: vignesh C <vignesh21@gmail.com>
Date: Tue, 18 Mar 2025 15:19:51 +0530
Message-ID: 
 <CALDaNm0WoB+w4qz4n1ms3hTfLeRGzmUvBjRH0Weod5gsVpJ5hg@mail.gmail.com>
Subject: Re: SQL:2011 application time
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Paul Jungwirth <pj@illuminatedcomputing.com>,
 jian he <jian.universality@gmail.com>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CALDaNm0WoB%2Bw4qz4n1ms3hTfLeRGzmUvBjRH0Weod5gsVpJ5hg%40mail.gmail.com>
Precedence: bulk

On Mon, 10 Mar 2025 at 16:26, Peter Eisentraut <peter@eisentraut.org> wrote:
>
> On 26.02.25 06:15, Paul Jungwirth wrote:
> >  > ON DELETE RESTRICT must be specified when PERIOD BUSINESS_TIME is
> > also specified.
> >
> > Here are some patches removing support for RESTRICT
>
> I have committed this.
>
> I think this is about as much as we can hope to get done from this patch
> series for PG18.  I don't think the subsequent patches are ready enough.
>   As an example, the FOR PORTION OF still has the problem I mentioned at
> <https://www.postgresql.org/message-id/d4c5de4d-ff2d-4ef6-b7a2-1787dfa6427b%40eisentraut.org>,
> and a few similar structural problems.  Also, I see that you have
> recently changed some things to make use of SPI, which seems
> problematic.  This needs much further analysis.
>
> My suggestions is to close the commitfest entry as "committed" and start
> new threads and new entries for the subsequent features.

I have marked this commitfest entry as committed based on your
suggestion. It is better to start a new thread for the remaining work.

Regards,
Vignesh