pgsql: pg_upgrade: Convert old visibility map format to new format. - Mailing list pgsql-committers

From Robert Haas
Subject pgsql: pg_upgrade: Convert old visibility map format to new format.
Date
Msg-id E1aeQzK-0004Pm-K0@gemulon.postgresql.org
Whole thread Raw
Responses Re: pgsql: pg_upgrade: Convert old visibility map format to new format.  (Bruce Momjian <bruce@momjian.us>)
List pgsql-committers
pg_upgrade: Convert old visibility map format to new format.

Commit a892234f830e832110f63fc0a2afce2fb21d1584 added a second bit per
page to the visibility map, but pg_upgrade has been unaware of it up
until now.  Therefore, a pg_upgrade from an earlier major release of
PostgreSQL to any commit preceding this one and following the one
mentioned above would result in invalid visibility map contents on the
new cluster, very possibly leading to data corruption.  This plugs
that hole.

Masahiko Sawada, reviewed by Jeff Janes, Bruce Momjian, Simon Riggs,
Michael Paquier, Andres Freund, me, and others.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/7087166a88fe0c04fc6636d0d6d6bea1737fc1fb

Modified Files
--------------
src/bin/pg_upgrade/file.c        | 154 +++++++++++++++++++++++++++++++++++++++
src/bin/pg_upgrade/pg_upgrade.h  |   6 ++
src/bin/pg_upgrade/relfilenode.c |  48 +++++++++---
3 files changed, 197 insertions(+), 11 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: When appropriate, postpone SELECT output expressions till after
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Only try to push down foreign joins if the user mapping OIDs mat