Re: Unique key constraint Issue - Mailing list pgsql-general

From shashidhar Reddy
Subject Re: Unique key constraint Issue
Date
Msg-id CAH=zU4uiEG_KRKT2DOpNKVdKoBvDWcV3eXvn4TNtohRtOTwdEA@mail.gmail.com
Whole thread Raw
In response to Re: Unique key constraint Issue  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Thank you Adrian.

We replicated the issue with OS upgrade.

On Tue, 26 Nov, 2024, 11:06 am Adrian Klaver, <adrian.klaver@aklaver.com> wrote:
On 11/25/24 19:07, shashidhar Reddy wrote:
> Hi Adrian,
>
> Thank you for your response.
>
> I don't think index corrupted as I can generate the ddl script from the

What DDL script?

> index and the index is still in use when we query.

See Tom Lanes post for more detail. Short version the index will still
'work' except for the part where it lets in duplicate entries.

>   To rebuild the index we are still removing duplicate entries. But
> nothing found in logs.
>
> On Mon, 25 Nov, 2024, 9:30 pm Adrian Klaver, <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.com>> wrote:
>
>     On 11/25/24 00:44, shashidhar Reddy wrote:
>      > Hi Ajit,
>      >
>      > Thank you for your reply!
>      >
>      > The result of the query is same across all servers and yes streaming
>      > replication does not have any issue but the question is how did
>      > duplicate values entered when there unique key in place.
>
>     Corrupted index?
>
>     Have you tried doing a REINDEX?
>
>
>     --
>     Adrian Klaver
>     adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>

--
Adrian Klaver
adrian.klaver@aklaver.com

pgsql-general by date:

Previous
From: shashidhar Reddy
Date:
Subject: Re: Unique key constraint Issue
Next
From: jayakumar s
Date:
Subject: Re: DB Switchover using repmgr--Error