Skip site navigation (1) Skip section navigation (2)

Re: Block-level CRC checks

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Aidan Van Dyk <aidan(at)highrise(dot)ca>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Block-level CRC checks
Date: 2009-12-01 19:51:08
Message-ID: 603c8f070912011151m4b08939y13fadd0b03060163@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Dec 1, 2009 at 2:06 PM, Aidan Van Dyk <aidan(at)highrise(dot)ca> wrote:
> Well, *I* think if we're ever going to have really reliable "in-place
> upgrades" that we can expect to function release after release, we're
> going to need to be able to read in "old version" pages, and convert
> them to current version pages, for some set of "old version" (I'ld be
> happy with $VERSION-1)...  But I don't see that happening any time
> soon...

I agree.  I've attempted to make this point before - as has Zdenek -
and been scorned for it, but I don't think it's become any less true
for all of that.  I don't think you have to look much further than the
limitations on upgrading from 8.3 to 8.4 to conclude that the current
strategy is always going to be pretty hit or miss.

http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/~checkout~/pg-migrator/pg_migrator/README?rev=1.59&content-type=text/plain

...Robert

In response to

Responses

pgsql-hackers by date

Next:From: Greg StarkDate: 2009-12-01 20:04:53
Subject: Re: Block-level CRC checks
Previous:From: Tom LaneDate: 2009-12-01 19:46:27
Subject: Re: SE-PgSQL patch review

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group