Re: Block-level CRC checks

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, decibel <decibel(at)decibel(dot)org>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, jd(at)commandprompt(dot)com, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Block-level CRC checks
Date: 2009-12-04 14:48:30
Message-ID: 20091204144830.GE4705@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas escribió:
> Simon Riggs wrote:
> > On Fri, 2009-12-04 at 09:52 -0300, Alvaro Herrera wrote:
> >
> >> BTW with VACUUM FULL removed I assume we're going to get rid of
> >> HEAP_MOVED_IN and HEAP_MOVED_OFF too, right?
> >
> > Much as I would like to see those go, no. VF code should remain for some
> > time yet, IMHO.
>
> I don't think we need to keep VF code otherwise, but I would leave
> HEAP_MOVED_IN/OFF support alone for now for in-place upgrade. Otherwise
> we need a pre-upgrade script or something to scrub them off.

CRCs are going to need scrubbing anyway, no? Oh, but you're assuming
that CRCs are optional, so not everybody would need that, right?

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-12-04 15:00:00 Re: Block-level CRC checks
Previous Message Alvaro Herrera 2009-12-04 14:46:01 Re: Block-level CRC checks