public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Paul Jungwirth <[email protected]>
Cc: jian he <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: vignesh C <[email protected]>
Subject: Re: SQL:2011 application time
Date: Tue, 21 Jan 2025 19:52:30 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mDHcY4_qQ0+noCUVg@mail.gmail.com>
	<CA+renyUFC13F0tYKxEENZtWA0YVuS5Tv+ZQkEkAwuDO1-Xke-A@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]>

On 12.01.25 00:19, Paul Jungwirth wrote:
> On 1/4/25 13:39, Paul Jungwirth wrote:
>> These updates fix a problem in the unaccent contrib module. When I 
>> added a new parameter to get_func_namespace, I changed a call there. 
>> Then I when took out that parameter, I didn't update the extension 
>> again. Otherwise these are the same as the v46 patches.
> 
> Hi Hackers,
> 
> Here is another set of commits. Based on discussion on the thread about 
> Index AM API Cleanup [1], I decided that I should just always make FOR 
> PORTION OF infer its intersect proc from whatever intersect op is used 
> by temporal foreign keys (even though we don't have a way to get an 
> intersect op for non-range/multirange types yet). This means we need one 
> less GiST support proc, which seems like a nice improvement.
> 
> I also fixed the RESTRICT commit where a change previously was included 
> in a later commit that should have been included there.
> 
> Rebased to 29dfffae0a, fixing a merge conflict + crash with the NOT 
> ENFORCED commit.

I have committed the fix for foreign key NO ACTION (patch 0002, this did 
not require patch 0001).  I will study the proposed fix for RESTRICT 
(patches 0001 and 0003) next.

view thread (23+ 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: <[email protected]>

* 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