Re: Checksums, state of play

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Checksums, state of play
Date: 2012-03-07 20:21:21
Message-ID: 18236.1331151681@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> So I think it's time to push this one out to 9.3.

Frankly, I thought it was probably too late for 9.2 when it was first
proposed, and the number of issues that have been identified since then
just confirm that feeling.

There is another point beyond the ones in your summary: if we squeeze
checksums into the page header without increasing its size, however we
do it there will be no going back, because we will certainly have used
up all the remaining wiggle room there. That means we'll be absolutely
committed to this implementation, permanently (or at least until we
invent the page format upgrade code that no one seems to want to build).
I think we need to be a lot more certain that we're happy with the
design and can't improve on it before we make that commitment.

What I'd like to see is for Simon to keep hacking on the identified
issues, with the hope of having a solid patch ready to commit early
in the 9.3 cycle.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2012-03-07 20:21:57 Re: Speed dblink using alternate libpq tuple storage
Previous Message Robert Haas 2012-03-07 20:21:03 Re: RFC: Making TRUNCATE more "MVCC-safe"