pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: hali19790320@gmail.com
Subject: BUG #16593: pg_upgrade make corrupt UK indexes
Date: Tue, 25 Aug 2020 22:55:52 +0000
Message-ID: <16593-875efda911c9b799@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16593
Logged by:          László Tóth
Email address:      hali19790320@gmail.com
PostgreSQL version: 9.6.19
Operating system:   centos7
Description:        

We upgrade from 9.6 Centos7 to 12.3 Centos 8

1. Stop 9.6
2. rsync 9.6 data and bin files from Centos7 to Centos8 (pre installed 12)
3. pg_upgrade
4. ./analyze_new_cluster.sh
5. ./delete_old_cluster.sh

We found amcheck and throwed exception!

But yes, by amcheck wiki 
https://www.postgresql.org/docs/10/amcheck.html

Whe select is a little bit missunderstandable. I think it will be a little
bit more understandable if write the function is for check one index. So the
query where statement (LIMIT 10 and AND n.nspname = 'pg_catalog' ) ignores a
lot of serious index validation! 

It will be very useful a checklist how can we be sure the upgrade is
succesful!

Thank you!

Here documented it:
https://stackoverflow.com/questions/63588123/postgres-pg-upgrade-corrupt-indexes-uk-missing-values-t...



view thread (5+ messages)  latest in thread

Message-ID: <16593-875efda911c9b799@postgresql.org>
Permalink:  ../16593-875efda911c9b799@postgresql.org/
Also on:    postgresql.org/message-id/16593-875efda911c9b799@postgresql.org

 · 

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: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, hali19790320@gmail.com
  Subject: Re: BUG #16593: pg_upgrade make corrupt UK indexes
  In-Reply-To: <16593-875efda911c9b799@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox