public inbox for [email protected]
help / color / mirror / Atom feedFrom: shashidhar Reddy <[email protected]>
To: Adrian Klaver <[email protected]>
Cc: ajit wangkhem <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Unique key constraint Issue
Date: Wed, 27 Nov 2024 08:02:45 +0530
Message-ID: <CAH=zU4uiEG_KRKT2DOpNKVdKoBvDWcV3eXvn4TNtohRtOTwdEA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAH=zU4t3KRpt6uTZn_4eKkvpL_X9ACGNZ+XDxfMjnn6ovAyPVQ@mail.gmail.com>
<CAMurXp115NcKB64EsksfSMJmztS_FBm0PuAmnXu_OXgh8MVz3w@mail.gmail.com>
<CAH=zU4tTUYCyhipNy-auv-Zum=CFiV0g1BURyFxrx7_nsv0Ucg@mail.gmail.com>
<[email protected]>
<CAH=zU4syqG08eH7+McKeVL1f+ggfBSbpe89R0wwmfcDhk_3kiQ@mail.gmail.com>
<[email protected]>
Thank you Adrian.
We replicated the issue with OS upgrade.
On Tue, 26 Nov, 2024, 11:06 am Adrian Klaver, <[email protected]>
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, <[email protected]
> > <mailto:[email protected]>> 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
> > [email protected] <mailto:[email protected]>
> >
>
> --
> Adrian Klaver
> [email protected]
>
>
view thread (4+ messages)
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Unique key constraint Issue
In-Reply-To: <CAH=zU4uiEG_KRKT2DOpNKVdKoBvDWcV3eXvn4TNtohRtOTwdEA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox