| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| 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:22:19 |
| Message-ID: | 18700.1168532539@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2007-01-11 16:25:12 | Re: wal buffers documentation -errata |
| Previous Message | Gregory Stark | 2007-01-11 16:18:36 | Re: [HACKERS] [PATCHES] wal_checksum = on (default) | off |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2007-01-11 16:25:12 | Re: wal buffers documentation -errata |
| Previous Message | Gregory Stark | 2007-01-11 16:18:36 | Re: [HACKERS] [PATCHES] wal_checksum = on (default) | off |