| From: | Brendan Jurd <direvus(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: generalized index constraints |
| Date: | 2009-09-15 16:44:23 |
| Message-ID: | 37ed240d0909150944s2024719fi40df523927c8d95c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2009/9/16 Robert Haas <robertmhaas(at)gmail(dot)com>:
> Instead of calling these generalized index constraints, I wonder if we
> oughtn't to be calling them something like "don't-overlap constraints"
> (that's a bad name, but something along those lines). They're not
> really general at all, except compared to uniqueness constraints (and
> they aren't called generalized unique-index constraints, just
> generalized index constraints).
Well "generalized index constraints" is what we're calling the patch,
but I don't think they are called by that name anywhere in the
proposed documentation changes. In the extension to ALTER TABLE
syntax, they are simply referred to as "index_constraint".
Cheers,
BJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-09-15 16:47:26 | Re: errcontext support in PL/Perl |
| Previous Message | Robert Haas | 2009-09-15 16:39:37 | Re: hardware information |