Re: Planning incompatibilities for Postgres 10.0 - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Planning incompatibilities for Postgres 10.0
Date
Msg-id 20130527190612.GU15045@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Planning incompatibilities for Postgres 10.0  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Planning incompatibilities for Postgres 10.0  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian wrote:

> OK, I have added a section to the TODO list for this:
> 
>     Desired changes that would prevent upgrades with pg_upgrade
>     
>         32-bit page checksums 
> 
> Are there any others?

I would have each data segment be self-identifying, i.e. have a magic
number at the beginning of the file and the relation OID, some fork
identification and the segment number somewhere -- probably the special
space of the first page.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Planning incompatibilities for Postgres 10.0
Next
From: Jaime Casanova
Date:
Subject: Re: New committers