From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | hali19790320(at)gmail(dot)com |
Subject: | BUG #16593: pg_upgrade make corrupt UK indexes |
Date: | 2020-08-25 22:55:52 |
Message-ID: | 16593-875efda911c9b799@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16593
Logged by: László Tóth
Email address: hali19790320(at)gmail(dot)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-though-missing-records-b
From | Date | Subject | |
---|---|---|---|
Next Message | Nick Cleaton | 2020-08-26 05:37:56 | Re: BUG #16593: pg_upgrade make corrupt UK indexes |
Previous Message | Alvaro Herrera | 2020-08-25 21:39:46 | Re: password saved in .psql_history |