Em sex, 5 de jul de 2019 às 07:37, Ronan Dunklau
escreveu:
> We ran into that while using wal2json, which uses the replication id index
> attnames to identify which columns are part of the primary key. If the
> primary key column has been renamed, we end with no information about the
> identit
Thank you for this quick answer, I'll report the bug to wal2json then.
Le ven. 5 juil. 2019 à 16:22, Tom Lane a écrit :
> Ronan Dunklau writes:
> > I've noticed that renaming an indexed column produces inconsistencies in
> > the catalog. Namely, the attname of the attribute of the relation is
>
Ronan Dunklau 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 use