From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Last gasp |
Date: | 2012-04-06 00:19:07 |
Message-ID: | 20120406001907.GB4451@tornado.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 05, 2012 at 02:34:30PM -0400, Robert Haas wrote:
> On Thu, Apr 5, 2012 at 2:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > The FK arrays one I'm kind of queasy about. ?It's a cool-sounding idea
> > but I'm not convinced that all the corner-case details have been
> > adequately thought through, and I'm scared of being unable to fix any
> > such bugs in later versions because of backwards compatibility worries.
> > It'd be a lot better to be pushing this in at the start of a devel cycle
> > than the end.
>
> I've been feeling that that patch has been suffering from a lack of
> reviewer attention, which is a real shame, because I think the
> functionality is indeed really cool. But I haven't looked at it
> enough to know what kind of shape it's in.
As the reviewer, I'm not aware of any unexplored corner cases or problems that
ought to preclude commit. That said, it is a large patch; I doubt anyone
could pick it up from scratch and commit it with less than a solid day's
effort, and 2-3 days might be more likely. In retrospect, I should have
suggested splitting the new ON DELETE/ON UPDATE actions into their own patch.
That would have nicely slimmed the base patch and also isolated it from the ON
DELETE EACH CASCADE judgement call.
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2012-04-06 00:22:03 | Re: System catalog typos |
Previous Message | Andrew Dunstan | 2012-04-06 00:12:53 | parallel dump/restore code on WIndows |