Re: Inconsistency between attname of index and attname of relation

From: Euler Taveira <euler(at)timbira(dot)com(dot)br>
To: Ronan Dunklau <ronan_dunklau(at)ultimatesoftware(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Inconsistency between attname of index and attname of relation
Date: 2019-07-05 15:19:24
Message-ID: CAHE3wghH97G4g1gamC2u1rJ=ftesv3xQtyCc0ELPa7qwgVXmbA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em sex, 5 de jul de 2019 às 07:37, Ronan Dunklau
<ronan_dunklau(at)ultimatesoftware(dot)com> 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 identity of the tuple being updated / deleted.
>
Ouch. That's a wal2json bug. I saw that you already opened an issue.

--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2019-07-05 16:04:56 Re: mcvstats serialization code is still shy of a load
Previous Message Tomas Vondra 2019-07-05 15:06:12 Re: mcv compiler warning