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 4943700c-fe86-1044-ee0d-069c8a134f6c@proxel.se
Whole thread Raw
In response to Re: [HACKERS] GSoC 2017: Foreign Key Arrays  (Mark Rofail <markm.rofail@gmail.com>)
Responses Re: [HACKERS] GSoC 2017: Foreign Key Arrays  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On 11/13/2017 12:32 PM, Mark Rofail wrote:
>         == The @>> operator
>         I would argue that allocating an array of datums and building an
>         array would have the same complexity
> 
> 
>     I am not sure what you mean here. Just because something has the
>     same complexity does not mean there can't be major performance
>     differences.
> 
> I have spend a lot of time working on this operator and would like to 
> benefit from it. How should I go about this ? Start a new patch ?

I am still not sure what you mean here. Feel free to add @>> to this 
patch if you like. You may want to submit it as two patch files (but 
please keep them as the same commitfest entry) but I leave that decision 
all up to you.
> So the two main issues we remain to resolve are MATCH FULL and the 
> RI_Initial_Check() query refactoring. The problem is that I am not one 
> of the original authors and have not touched this part of the code.
> I understand the problem but it will take some time for me to understand 
> how to resolve everything.

Cool, feel free to ask if you need some assistance. I want this patch.

Andreas


pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: [HACKERS] GnuTLS support
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager