| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Checksums by default? |
| Date: | 2017-02-03 23:23:15 |
| Message-ID: | ee13594c-fad1-37c7-0ebe-e3228080db1d@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/25/17 6:40 PM, Stephen Frost wrote:
> Obviously, having to bring up a full database is an extra step (one we
> try to make easy to do), but, sadly, we don't have any way to ask PG to
> verify all the checksums with released versions, so that's what we're
> working with.
Wouldn't it be fairly trivial to write an extension that did that though?
foreach r in pg_class where relkind in (...)
for (b = 0; b < r.relpages; b++)
ReadBufferExtended(..., BAS_BULKREAD);
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-02-03 23:31:25 | Re: Checksums by default? |
| Previous Message | Jeff Janes | 2017-02-03 23:07:02 | Re: Write Ahead Logging for Hash Indexes |