Re: [PATCH] Support for Array ELEMENT Foreign Keys - Mailing list pgsql-hackers

From Thom Brown
Subject Re: [PATCH] Support for Array ELEMENT Foreign Keys
Date
Msg-id CAA-aLv437K=j24LuGoeOaz=Y6NN5o5tvMfMay=_7LtaEmVWz=Q@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Support for Array ELEMENT Foreign Keys  (Thom Brown <thom@linux.com>)
List pgsql-hackers
On 25 October 2014 19:19, Thom Brown <thom@linux.com> wrote:
On 25 October 2014 13:28, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Thom Brown wrote:
> On 24 October 2012 18:17, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> > Marco Nenciarini <marco.nenciarini@2ndquadrant.it> writes:
> > > Please find the attached refreshed patch (v2) which fixes the loose ends
> > > you found.
> >
> > Attached is a v3 patch that updates the syntax per discussion, uses what
> > seems to me to be a saner (more extensible) catalog representation, and
> > contains assorted other code cleanup.  I have not touched the
> > documentation at all except for catalogs.sgml, so it still explains the
> > old syntax.  I have to stop working on this now, because I've already
> > expended more time on it than I should, and it still has the serious
> > problems mentioned in
> > http://archives.postgresql.org/message-id/16787.1351053391@sss.pgh.pa.us
> > and
> > http://archives.postgresql.org/message-id/28389.1351094795@sss.pgh.pa.us
> >
> > I'm going to mark this Returned With Feedback for the current CF.
> >
>
> Does anyone have any intention of resurrecting this at this stage?

Not in this room.  Do you?

I'm not qualified to, but I'm happy to make time to test it when it next gets picked up.  My email was really just bumping the topic.

I should mention that the latest patch no longer applies against git master, so I can't test it in its current form.
--
Thom

pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: How ugly would this be? (ALTER DATABASE)
Next
From: Haribabu Kommi
Date:
Subject: Possible problem with shm_mq spin lock