| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | David Christensen <david(at)endpoint(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: [DESIGN] Incremental checksums |
| Date: | 2015-07-13 21:16:51 |
| Message-ID: | 20150713211651.GD25610@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-07-13 15:50:44 -0500, Jim Nasby wrote:
> Another possibility is some kind of a page-level indicator of what binary
> format is in use on a given page. For checksums maybe a single bit would
> suffice (indicating that you should verify the page checksum). Another use
> case is using this to finally ditch all the old VACUUM FULL code in
> HeapTupleSatisfies*().
That's a bad idea, because that bit then'd not be protected by the
checksum.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-07-13 21:18:47 | Re: PostgreSQL 9.5 Alpha 1 build fail with perl 5.22 |
| Previous Message | Tom Lane | 2015-07-13 21:12:51 | Re: [PATCH] SQL function to report log message |