From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, decibel <decibel(at)decibel(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Page-level version upgrade (was: Block-level CRC checks) |
Date: | 2009-12-02 20:48:01 |
Message-ID: | 22020.1259786881@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> This whole discussion is based on assumptions which do not match my
> recollection of the old discussion. I would suggest people go back and
> read the emails but it's clear at least some people have so it seems
> people get different things out of those old emails. My recollection
> of Tom and Heikki's suggestions for Zdenek were as follows:
> 1) When 8.9.0 comes out we also release an 8.8.x which contains a new
> guc which says to prepare for an 8.9 update.
Yeah, I think the critical point is not to assume that the behavior of
the old system is completely set in stone. We can insist that you must
update to at least point release .N before beginning the migration
process. That gives us a chance to backpatch code that makes
adjustments to the behavior of the old server, so long as the backpatch
isn't invasive enough to raise stability concerns.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2009-12-02 21:18:35 | Re: YAML Was: CommitFest status/management |
Previous Message | Greg Stark | 2009-12-02 20:46:22 | Re: [CORE] EOL for 7.4? |