Re: FK's to refer to rows in inheritance child

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, YebHavinga <yebhavinga(at)gmail(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, "w(dot)p(dot)dijkstra(at)mgrid(dot)net" <w(dot)p(dot)dijkstra(at)mgrid(dot)net>
Subject: Re: FK's to refer to rows in inheritance child
Date: 2010-12-05 14:37:51
Message-ID: 4CFBA3BF.4070009@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/04/2010 07:12 PM, Robert Haas wrote:
>
> I wouldn't necessarily be opposed to official topic branches at some point in the future, but I think it's premature to speculate about whether it'd be useful here.

I'd need a lot of convincing if it imposed an extra burden on people
like Tom. The only way I could see working is if some committer took
ownership of the topic branch and guaranteed to keep it pretty much in
sync with the master branch.

> What is needed right now is design work, not code.
>

Indeed. In this case I don't think we even have agreement on the
features let alone how they might work.

cheers

andreew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2010-12-05 15:11:35 serializable read only deferrable
Previous Message Kevin Grittner 2010-12-05 14:30:25 Re: what are clog and xlog?