public inbox for [email protected]  

help / color / mirror / Atom feed

From: vignesh C <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: Paul Jungwirth <[email protected]>
Cc: jian he <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: SQL:2011 application time
Date: Tue, 18 Mar 2025 15:19:51 +0530
Message-ID: <CALDaNm0WoB+w4qz4n1ms3hTfLeRGzmUvBjRH0Weod5gsVpJ5hg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mDHcY4_qQ0+noCUVg@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Mon, 10 Mar 2025 at 16:26, Peter Eisentraut <[email protected]> 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

view thread (35+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: SQL:2011 application time
  In-Reply-To: <CALDaNm0WoB+w4qz4n1ms3hTfLeRGzmUvBjRH0Weod5gsVpJ5hg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox