pg_upgrade from 9.4 to 10.4

From: Vimalraj A <vimal1805(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: pg_upgrade from 9.4 to 10.4
Date: 2018-06-15 22:01:37
Message-ID: CAFKBAK5e4Q-oTUuPPJ56EU_d2Rzodq6GWKS3ncAk3xo7hAsOZg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

Hi,

After pg_upgrade, the data in Postgres is corrupted.

1. Postgres 9.4, stop db with "immediate" mode
2. Run pg_upgrade, to upgrade to Postgres 10.4
3. Start Postgres 10 and run vacuum full, got a bunch of "concurrent insert
in progress". Looks like the data is corrupted. (Loading the old data back
on Postgres 9.4 works just fine)

But if I stop the 9.4 DB with "smart" mode, the data after pg_upgrade looks
fine.

pg_upgrade doesn't stop or throw warnings if the upgraded db gets into
corrupted state.

I would like to understand why it happens so.
1. What transient state corrupts the db?
2. Is it a known issue with pg_upgrade?
3. Is there a way to get the data from pg_upgrade after "immediate" mode
stop of previous version?

Thank you.

Regards,
Vimal.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2018-06-15 23:46:44 Re: Making all nbtree entries unique by having heap TIDs participate in comparisons
Previous Message Robert Haas 2018-06-15 21:36:10 Re: Making all nbtree entries unique by having heap TIDs participate in comparisons