Quick Links

Re: GSoC 2017: Foreign Key Arrays

From:	Mark Rofail <markm(dot)rofail(at)gmail(dot)com>
To:	Erik Rijkers <er(at)xs4all(dot)nl>
Cc:	Robert Haas <robertmhaas(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, David Steele <david(at)pgmasters(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers-owner(at)postgresql(dot)org
Subject:	Re: GSoC 2017: Foreign Key Arrays
Date:	2017-07-27 19:08:51
Message-ID:	CAJvoCuuDJowgZvxJWWn=pB0QZTF6WC1bCG=uity8XmqTwEAk6g@mail.gmail.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

On Thu, Jul 27, 2017 at 7:15 PM, Erik Rijkers <er(at)xs4all(dot)nl> wrote:

> It would help (me at least) if you could be more explicit about what
> exactly each instance is.
>

I apologize, I thought it was clear through the context.

I meant by the original patch is all the work done before my GSoC project.
The latest of which, was submitted by Tom Lane[1]. And rebased here[2].

The new patch is the latest one submitted by me[3].

And the new patch with index is the same[3], but with a GIN index built
over it. CREATE INDEX ON fktableforarray USING gin (fktest array_ops);

Best Regards,
Mark Rofail

	From	Date	Subject
Next Message	Mark Rofail	2017-07-27 19:15:28	Re: GSoC 2017: Foreign Key Arrays
Previous Message	Robert Haas	2017-07-27 18:58:58	Re: Change in "policy" on dump ordering?