Re: Block-level CRC checks

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Greg Stark" <greg(dot)stark(at)enterprisedb(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Block-level CRC checks
Date: 2008-12-15 16:38:49
Message-ID: 36e682920812150838o6f63c7b5l54b0b92c363954b9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 15, 2008 at 11:29 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com> writes:
>> On Mon, Dec 15, 2008 at 10:13 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>>> Feature freeze is not the time to be looking for new ideas. I suggest
>>> we save this for 8.5.
>
>> Well, we may not need a new idea.
>
> We don't really have an acceptable solution for the conflict with hint
> bit behavior. The shutdown issue is minor, agreed, but that's not the
> stumbling block.

Agreed on the shutdown issue. But, didn't this patch address the hint
bit setting as discussed? After performing a cursory look at the
patch, it appears that hint-bit changes are detected and a WAL entry
is written on buffer flush if hint bits had been changed. I don't see
anything wrong with this in theory. Am I missing something?

Now, in the case where hint bits have been updated and a WAL record is
required because the buffer is being flushed, requiring the WAL to be
flushed up to that point may be a killer on performance. Has anyone
tested it?

--
Jonah H. Harris, Senior DBA
myYearbook.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-12-15 16:38:53 Re: Restore enforce_generic_type_consistency's breaks a farms
Previous Message Robert Treat 2008-12-15 16:37:29 Re: plperl: Documentation on BYTEA decoding is wrong