Re: Inconsistency between attname of index and attname of relation - Mailing list pgsql-hackers

From Ronan Dunklau
Subject Re: Inconsistency between attname of index and attname of relation
Date
Msg-id CAA8M49rWpMuv9nOUdRPn-TPF_gBhTyU=Shbc0+nOXuuL1zGjYA@mail.gmail.com
Whole thread Raw
In response to Re: Inconsistency between attname of index and attname of relation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Thank you for this quick answer, I'll report the bug to wal2json then.

Le ven. 5 juil. 2019 à 16:22, Tom Lane <tgl@sss.pgh.pa.us> a écrit :
Ronan Dunklau <ronan_dunklau@ultimatesoftware.com> writes:
> I've noticed that renaming an indexed column produces inconsistencies in
> the catalog. Namely, the attname of the attribute of the relation is
> properly updated, whereas the attname of the attribute in the index is not,
> and keeps the old value.

If memory serves, we used to try to rename index columns, and gave up
on that because it caused problems of its own.  That's (one reason) why
modern versions of psql show a "definition" column in \d of an index.

> I think this could be considered a bug in Postgres.

It is not.

> If it isn't, what
> should be the proper way to retrieve this information ?

psql uses pg_get_indexdef(), looks like.

                        regards, tom lane



This e-mail message and any attachments to it are intended only for the named recipients and may contain legally privileged and/or confidential information. If you are not one of the intended recipients, do not duplicate or forward this e-mail message.

pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: "WIP: Data at rest encryption" patch and, PostgreSQL 11-beta3
Next
From: Tomas Vondra
Date:
Subject: Re: mcv compiler warning