Re: Index corruption revealed after upgrade to 11.17, could date back to at least 11.12 - Mailing list pgsql-general

From Allan Kamau
Subject Re: Index corruption revealed after upgrade to 11.17, could date back to at least 11.12
Date
Msg-id CAF3N6oR7Q2f=e68U_vs5MW9u5ru37tcYVjEs+FnK-5Ze8rpgoQ@mail.gmail.com
Whole thread Raw
In response to Re: Index corruption revealed after upgrade to 11.17, could date back to at least 11.12  ("Peter J. Holzer" <hjp-pgsql@hjp.at>)
List pgsql-general


On Thu, Oct 27, 2022 at 12:18 PM Peter J. Holzer <hjp-pgsql@hjp.at> wrote:
On 2022-10-27 10:55:31 +0300, Kristjan Mustkivi wrote:
> We use dockerized postgres.

So that means you aren't just replacing PostgreSQL, but your complete OS
(except the kernel). What is the source of your docker images? Do they
all use the same base OS distribution? Are the locale definitions the
same?

(Just trying to rule other other possible error sources.)


> I do apologize, but I do not understand the value of doing that select
> juggling.

I think Allan may have misread your mail.

        hp

--
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"



Hi Peter,

It was a long shot. I was trying to suggest determining if indeed the data does actually contain duplicating values in the mentioned columns. 
Then test to see if the index construction on the new table can be successful on both versions and see if the error is reproducible.

-Allan.

pgsql-general by date:

Previous
From: "Peter J. Holzer"
Date:
Subject: Re: Index corruption revealed after upgrade to 11.17, could date back to at least 11.12
Next
From: Kristjan Mustkivi
Date:
Subject: Re: Index corruption revealed after upgrade to 11.17, could date back to at least 11.12