Date: Tue, 10 Apr 2018 10:59:17 -0300
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Mark Rofail <markm.rofail@gmail.com>
Cc: David Steele <david@pgmasters.net>,
	Andreas Karlsson <andreas@proxel.se>,
	Alexander Korotkov <aekorotkov@gmail.com>,
	Erik Rijkers <er@xs4all.nl>,
	=?iso-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <hs@cybertec.at>,
	Robert Haas <robertmhaas@gmail.com>,
	Stephen Frost <sfrost@snowman.net>, Tom Lane <tgl@sss.pgh.pa.us>,
	pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Message-ID: <20180410135917.odjh5coa4cjatz5v@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAJvoCuvdSx8fizeFYLLf6xeJHG6mDF+z2vcuKKrD25RBahjX8Q@mail.gmail.com>
User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0)
Precedence: bulk

Mark Rofail wrote:
> Hello David,
> 
> On Tue, Apr 10, 2018 at 3:47 PM, David Steele <david@pgmasters.net> wrote:
> 
> > You should produce a new version by then that addresses Alvaro's
> > concerns and I imagine that will require quite a bit of discussion and
> > work.
> 
> I'll get working.
> I'll produce a patch with two alternate versions, one with and one without
> the GIN operators.

I'd rather see one patch with just the GIN operator (you may think it's
a very small patch, but that's only because you forget to add
documentation to it and a few extensive tests to ensure it works well);
then the array-fk stuff as a follow-on patch.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services