From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: patch: Distinguish between unique indexes and unique constraints |
Date: | 2010-04-18 15:18:11 |
Message-ID: | g2r603c8f071004180818v7690a2fcj788db9dc5325f276@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Apr 17, 2010 at 11:53 PM, Josh Kupershmidt <schmiddy(at)gmail(dot)com> wrote:
> Addressing TODO item "Distinguish between unique indexes and unique
> constraints in \d+" for psql, and picking up from thread:
> http://archives.postgresql.org/message-id/8780.1271187360@sss.pgh.pa.us
>
> Attached is a simple patch which clarifies unique constraints with
> "UNIQUE CONSTRAINT" in psql's \d+ description of a table. The
> appearance of unique indexes is left as-is.
>
> == Old \d+ display ==
> Indexes:
> "name_uniq_constr" UNIQUE, btree (name)
>
> == New \d+ display ==
> Indexes:
> "name_uniq_constr" UNIQUE CONSTRAINT, btree (name)
You know, I've never really understood the difference between these
two types of things, or why we need to support both. Which may be
just because I'm slow?
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-04-18 15:23:06 | Re: patch: Distinguish between unique indexes and unique constraints |
Previous Message | Simon Riggs | 2010-04-18 11:01:05 | Re: testing HS/SR - 1 vs 2 performance |