public inbox for [email protected]
help / color / mirror / Atom feedRe: Unique key constraint Issue
4+ messages / 2 participants
[nested] [flat]
* Re: Unique key constraint Issue
@ 2024-11-25 16:00 Adrian Klaver <[email protected]>
2024-11-26 03:07 ` Re: Unique key constraint Issue shashidhar Reddy <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Adrian Klaver @ 2024-11-25 16:00 UTC (permalink / raw)
To: shashidhar Reddy <[email protected]>; ajit wangkhem <[email protected]>; +Cc: pgsql-general
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]
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Unique key constraint Issue
2024-11-25 16:00 Re: Unique key constraint Issue Adrian Klaver <[email protected]>
@ 2024-11-26 03:07 ` shashidhar Reddy <[email protected]>
2024-11-26 05:36 ` Re: Unique key constraint Issue Adrian Klaver <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: shashidhar Reddy @ 2024-11-26 03:07 UTC (permalink / raw)
To: Adrian Klaver <[email protected]>; +Cc: ajit wangkhem <[email protected]>; pgsql-general
Hi Adrian,
Thank you for your response.
I don't think index corrupted as I can generate the ddl script from the
index and the index is still in use when we query.
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]>
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]
>
>
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Unique key constraint Issue
2024-11-25 16:00 Re: Unique key constraint Issue Adrian Klaver <[email protected]>
2024-11-26 03:07 ` Re: Unique key constraint Issue shashidhar Reddy <[email protected]>
@ 2024-11-26 05:36 ` Adrian Klaver <[email protected]>
2024-11-27 02:32 ` Re: Unique key constraint Issue shashidhar Reddy <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Adrian Klaver @ 2024-11-26 05:36 UTC (permalink / raw)
To: shashidhar Reddy <[email protected]>; +Cc: ajit wangkhem <[email protected]>; 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, <[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]
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Unique key constraint Issue
2024-11-25 16:00 Re: Unique key constraint Issue Adrian Klaver <[email protected]>
2024-11-26 03:07 ` Re: Unique key constraint Issue shashidhar Reddy <[email protected]>
2024-11-26 05:36 ` Re: Unique key constraint Issue Adrian Klaver <[email protected]>
@ 2024-11-27 02:32 ` shashidhar Reddy <[email protected]>
0 siblings, 0 replies; 4+ messages in thread
From: shashidhar Reddy @ 2024-11-27 02:32 UTC (permalink / raw)
To: Adrian Klaver <[email protected]>; +Cc: ajit wangkhem <[email protected]>; pgsql-general
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]
>
>
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2024-11-27 02:32 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-11-25 16:00 Re: Unique key constraint Issue Adrian Klaver <[email protected]>
2024-11-26 03:07 ` shashidhar Reddy <[email protected]>
2024-11-26 05:36 ` Adrian Klaver <[email protected]>
2024-11-27 02:32 ` shashidhar Reddy <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox