Postgres Pro
Downloads
Home   >   mailing lists

Re: SQL:2011 application time - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: SQL:2011 application time
Date
Msg-id 6ac43c8e-5595-40d9-a039-ede12e7487e1@eisentraut.org
Whole thread Raw
In response to Re: SQL:2011 application time  (Paul Jungwirth <pj@illuminatedcomputing.com>)
Responses Re: SQL:2011 application time
Re: SQL:2011 application time
List pgsql-hackers
Tree view 
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.

pgsql-hackers by date:

Previous
From: Bykov Ivan
Date:
Subject: RE: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Selectively invalidate caches in pgoutput module