Re: COMMENT ON INDEX silently fails

From: Michael Herold <quabla(at)hemio(dot)de>
To: David Fetter <david(at)fetter(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: COMMENT ON INDEX silently fails
Date: 2016-09-30 19:25:05
Message-ID: 1475263505.3787.0@mail.hemio.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


> Sure it does.

Okay, correct phrasing would be: It has unexpected effects.

> I suspect you were expecting the comment to be displayed in some
> place it
> isn't, but that's hard to discuss intelligently when you didn't say
> where
> you expected it to show up.

create table foo (f1 int primary key);
comment on index foo_pkey is 'test comment';
comment on constraint foo_pkey on foo is 'test comment 2';

# \di+
List of relations
Schema | Name | Type | Owner | Table | Size | Description
--------+----------+-------+----------+-------+------------+--------------
public | foo_pkey | index | postgres | foo | 8192 bytes | test comment
(1 row)

# SELECT * FROM pg_description WHERE description LIKE 'test com%';
objoid | classoid | objsubid | description
--------+----------+----------+----------------
123732 | 1259 | 0 | test comment
123733 | 2606 | 0 | test comment 2
(2 rows)

$ pgAdmin III

Before `comment on constraint` the textarea for comment is empty and no
statement for comment in SQL pane.

Afterwards it is using 'test comment 2'.

Best,
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-09-30 19:34:49 Re: COMMENT ON INDEX silently fails
Previous Message Reyes Ponce 2016-09-30 19:19:38 Re: BUG #14343: UPSERT (ON CONFLICT) doesn't check ON CONFLICT constraint first