From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Markus Schiltknecht <markus(at)bluegap(dot)ch> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, NikhilS <nikkhils(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Auto Partitioning |
Date: | 2007-04-06 05:56:36 |
Message-ID: | 28487.1175838996@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Markus Schiltknecht <markus(at)bluegap(dot)ch> writes:
> Uh.. can you elaborate on that? AFAICS, you would simply have to query
> multiple btree indexes and make sure non of them is violated.
That only works for the partition-key indexes, ie, ones where you can be
sure a-priori that there cannot be duplicate keys in two different indexes.
I believe the complaint here is that people would like to be able to
enforce uniqueness across the whole partitioned table on columns that
are not part of the partition key.
(But that sounds rather like pie in the sky, actually. Which other
databases can do that, and how do they do it?)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | ITAGAKI Takahiro | 2007-04-06 06:05:35 | Re: [PATCHES] Fix mdsync never-ending loop problem |
Previous Message | Greg Smith | 2007-04-06 05:47:53 | Re: Load distributed checkpoint V3 |
From | Date | Subject | |
---|---|---|---|
Next Message | ITAGAKI Takahiro | 2007-04-06 06:05:35 | Re: [PATCHES] Fix mdsync never-ending loop problem |
Previous Message | Greg Smith | 2007-04-06 05:47:53 | Re: Load distributed checkpoint V3 |