Re: [HACKERS] GSoC 2017: Foreign Key Arrays - Mailing list pgsql-hackers

From Andreas Karlsson
Subject Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Date
Msg-id 32b5834c-e77e-e9fa-0800-600295b75163@proxel.se
Whole thread Raw
In response to Re: [HACKERS] GSoC 2017: Foreign Key Arrays  ("Joel Jacobson" <joel@compiler.org>)
Responses Re: [HACKERS] GSoC 2017: Foreign Key Arrays
List pgsql-hackers
On 3/15/21 4:29 PM, Mark Rofail wrote:
> Actually, your fix led me in the right way, the issue was how windows 
> handle pointers.

Hi,

I have started working on a partially new strategy for the second patch. 
The ideas are:

1. I have removed the dependency on count(DISTINCT ...) by using an 
anti-join instead (this was implemented by Joel Jacobson with cleanup 
and finishing touches by me). The code is much clearer now IMHO.

2. That instead of selecting operators at execution time we save which 
operators to use in pg_constraint. This is heavily a work in progress in 
my attached patches. I am not 100% convinced this is the right way to go 
but I plan to work some on this this weekend to see how ti will work out.

Another thing I will look into is you gin patch. While you fixed it for 
simple scalar types which fit into the Datum type I wonder if we do not 
also need to copy types which are too large to fit into a Datum but I 
have not investigated yet which memory context the datum passed to 
ginqueryarrayextract() is allocated in.

Andreas


Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: New IndexAM API controlling index vacuum strategies
Next
From: Masahiro Ikeda
Date:
Subject: make the stats collector shutdown without writing the statsfiles if the immediate shutdown is requested.