Re: Planning incompatibilities for Postgres 10.0

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Mon, May 27, 2013 at 09:17:50AM -0400, Bruce Momjian wrote:
>> Yes, we should be collecting things we want to do for a pg_upgrade break
>> so we can see the list all in one place.

> 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?

GiST indexes really oughta have a metapage so there can be a version
number in them.

Also, if we are going to unify hstore and json, it'd be nice if we could
change the existing binary representation of hstore (per discussions at
Oleg and Teodor's talk --- this will be moot if we invent a new core
type, but it'd be better not to have to).

There are probably some other data-type-specific cleanups we could
make, but I have to go get on an airplane so no time to think about it.

regards, tom lane