From: | Yeb Havinga <yebhavinga(at)gmail(dot)com> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Greg Stark <gsstark(at)mit(dot)edu>, 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-04 19:08:20 |
Message-ID: | 4CFA91A4.9060806@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2010-12-04 19:22, Dimitri Fontaine wrote:
>
> That's calling for a try :)
>
> What about a new index type that follows the partitioning scheme in its
> root pages in a way that allow the locking to occur in a subpart of it,
> rather than for the whole index.
Would that (global) index be totally ordered? That seems a prerequisite
for unique constraint checking with _bt_doinsert.
regards,
Yeb Havinga
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2010-12-04 19:43:31 | Re: FK's to refer to rows in inheritance child |
Previous Message | Andrew Dunstan | 2010-12-04 18:56:35 | Re: FK's to refer to rows in inheritance child |