Renaming the primary key of a table blows everything up

[sgrif]

A project with the following migration would fail to compile when using infer_schema!

CREATE TABLE users (non_standard_pk SERIAL PRIMARY KEY);
ALTER TABLE users RENAME COLUMN non_standard_pk TO id;

While the column has been renamed, the pg_attribute entry that the index is pointing to continues to have the old name. This causes our generated code to explode when we do type PrimaryKey = users::non_standard_pk. I haven't looked too deeply into this. My guess is that there is some indicator on the pg_attribute entry which will indicate that it's no longer being directly used, and the new entry is somehow referencing the old one.

[sgrif]

Probably worth mentioning that the value of attisdropped on the entry with the wrong name is 'f'

[Eijebong]

I tried it and can't reproduce. Has this been fixed and the issue forgotten ? Maybe postgres has been fixed ?