From: Scott Ribe <scott_ribe@elevated-dev.com>
To: jwiencek3 <jwiencek3@comcast.net>
Cc: Teju Jakkidi vlogs <teja.jakkidi05@gmail.com>
Cc: Samed YILDIRIM <samed@reddoc.net>
Cc: Holger Jakobs <holger@jakobs.com>
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Duplicate data even with primary keys enabled
Date: Mon, 31 Oct 2022 11:19:14 -0600
Message-ID: <751E945F-B11B-4A34-AE93-63046AF3D26A@elevated-dev.com> (raw)
In-Reply-To: <pYHRoJlPmaTk4pYHSoYcxZ.1667236140.86c55dda85f836bc016474f6564bd70e.MISSINGID@comcast.net>
References: <pYHRoJlPmaTk4pYHSoYcxZ.1667236140.86c55dda85f836bc016474f6564bd70e.MISSINGID@comcast.net>
> On Oct 31, 2022, at 11:08 AM, jwiencek3 <jwiencek3@comcast.net> wrote:
>
> Have you tried dropping the index and then recreating it ?
Recreate or reindex are good things to try. BUT DEFINITELY CHECK INDEX DEFINITION BEFORE DROPPING
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, jwiencek3@comcast.net, teja.jakkidi05@gmail.com, samed@reddoc.net, holger@jakobs.com, pgsql-admin@lists.postgresql.org
Subject: Re: Duplicate data even with primary keys enabled
In-Reply-To: <751E945F-B11B-4A34-AE93-63046AF3D26A@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox