| From: | Markus Schiltknecht <markus(at)bluegap(dot)ch> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, NikhilS <nikkhils(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Auto Partitioning |
| Date: | 2007-04-04 20:30:12 |
| Message-ID: | 46140AD4.20002@bluegap.ch |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Hi,
Andrew Dunstan wrote:
> I guess my point was really that multi-table indexes might have uses
> beyond partitioning.
Aha, now I understand. Thanks for the clarification.
> Say I have two tables, each with a field FKed to a field in a third
> table. I'd like to create the values to be unique across the referring
> tables. Now, there are various tricks that can be played either with
> custom triggers or redundant data to do this, but there's no easy way.
> However, a multi-table unique index would do it for me quite nicely, if
> we could create such a thing.
Maybe going into a similar direction and better think of it as a
multi-table uniqueness constraint, which internally uses multiple,
single-table indexes?
Regards
Markus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-04-04 20:43:34 | Re: build/install xml2 when configured with libxml |
| Previous Message | Simon Riggs | 2007-04-04 20:29:08 | Re: Auto Partitioning |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-04-04 20:43:34 | Re: build/install xml2 when configured with libxml |
| Previous Message | Simon Riggs | 2007-04-04 20:29:08 | Re: Auto Partitioning |