| From: | Michael Herold <quabla(at)hemio(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Fetter <david(at)fetter(dot)org>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: COMMENT ON INDEX silently fails |
| Date: | 2016-09-30 19:46:07 |
| Message-ID: | 1475264767.3787.1@mail.hemio.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Sep 30, 2016 at 9:36 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Well, you should take that up with the pgAdmin crew, but I'd note that
> a comment on a constraint and a comment on the index underlying the
> constraint are two different things.
Seems like pgAdmin is hiding this on purpose, which makes kind of sense.
Seems like I missed "PostgreSQL automatically creates an index for each
unique constraint and primary key constraint to enforce uniqueness."
No Bugs here.
Best,
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-10-01 12:21:38 | Re: BUG #14343: UPSERT (ON CONFLICT) doesn't check ON CONFLICT constraint first |
| Previous Message | Tom Lane | 2016-09-30 19:36:44 | Re: COMMENT ON INDEX silently fails |