Re: Unique key constraint Issue

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: shashidhar Reddy <shashidharreddy001(at)gmail(dot)com>
Cc: ajit wangkhem <ajit(dot)wangkhem(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unique key constraint Issue
Date: 2024-11-26 05:36:47
Message-ID: 24e0eb89-9cb3-4fc5-baa9-af1bb8036796@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)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(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message prashant sinha 2024-11-26 06:04:28 Re: License question
Previous Message Subhash Udata 2024-11-26 04:08:26 Re: Questions on Upgrading PostgreSQL from 15.0 to 15.9 and Setting Up Streaming Replication