Re: Index corruption revealed after upgrade to 11.17, could date back to at least 11.12

On 2022-10-27 15:07:06 +0300, Kristjan Mustkivi wrote:
> On Thu, Oct 27, 2022 at 12:18 PM Peter J. Holzer <hjp-pgsql(at)hjp(dot)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.)
>
> Up until 11.17, the source of the docker images was tag "postgres:11"
> (from https://hub.docker.com/_/postgres) for 11.17 the tag became
> "postgres:11-bullseye" but as far as i could tell it was just a
> difference of tagging policy there. Everything else is kept the same
> when building our custom docker image (with pg_cron, wal2json and
> oracle_fdw). But.. I can see for example, that the PG 11.12 docker
> image used Debian 9.13 (PG 11.17 uses Debian 11.5 according to
> /etc/debian_version).

Ok, So that's an ugrade from Debian 9 to Debian 11. That's definitely
not just a "difference of tagging policy", That's two major versions of
the OS!

I don't remember exactly when the big incompatible libc upgrade was, but
it was very likely somewhere between Debian 9 and Debian 11, so you have
to rebuild all you indexes. Since you didn't do that immediately after
the upgrade you now have data corruption which you have to fix manually.

hp

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