Horton

Re: 16-bit page checksums for 9.2

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2012-03-01T21:08:26Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Wakeup WALWriter as needed for asynchronous commit performance.

Robert Haas <robertmhaas@gmail.com> writes:
>> So a relation can't have some pages in Version 9.2, and other pages in
>> version 9.3? How will this work for 2TB tables?

> Not very well, but better than Tom's proposal to require upgrading the
> entire cluster in a single off-line operation.

WTF?  That was most certainly not what *I* was proposing; it's obviously
unworkable.  We need a process that can incrementally up-version a live
database and keep track of the minimum version present, at some
granularity smaller than "whole database".

All of this was discussed and hashed out about two years ago, IIRC.
We just haven't made any progress towards actually implementing those
concepts.

			regards, tom lane