Re: [HACKERS] [PATCHES] wal_checksum = on (default) | off

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Jim Nasby" <decibel(at)decibel(dot)org>, "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>, <pgsql-hackers(at)postgresql(dot)org>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] [PATCHES] wal_checksum = on (default) | off
Date: 2007-01-11 16:25:28
Message-ID: 87mz4pwmx3.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
>> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>>> Pretty much not happening; or are you volunteering to fix every part of
>>> the system to tolerate injections of inserted data anywhere in a stored
>>> datum?
>
>> I was thinking to do it at a low level as the xlog records are prepared to be
>> written to the filesystem and as the data is being read from disk. I haven't
>> read that code yet to see where to inject it but I understand there's already
>> a copy happening and it could be done there.
>
> You understand wrong ... a tuple sitting on disk is normally read
> directly from the shared buffer, and I don't think we want to pay for
> copying it.

"xlog records"

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-01-11 16:37:38 Re: [HACKERS] [PATCHES] wal_checksum = on (default) | off
Previous Message Dave Cramer 2007-01-11 16:25:12 Re: wal buffers documentation -errata

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-01-11 16:37:38 Re: [HACKERS] [PATCHES] wal_checksum = on (default) | off
Previous Message Dave Cramer 2007-01-11 16:25:12 Re: wal buffers documentation -errata