| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: removing PD_ALL_VISIBLE |
| Date: | 2013-05-31 18:00:19 |
| Message-ID: | 51A8E533.5080109@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce,
> Roberts statement was:
>
>> Loss or corruption of a single visibility map page means possible loss
>> of half a gigabyte of data.
I fail to be alarmed at this; currently losing a single page of the clog
causes just as widespread corruption (worse, actually, since it's not
confined to one table). It does point to the eventual need to checksum
these things, though.
> Certainly unidentified corruption of a visibility map page could easily
> cause incorrect results. So, technically, _adding_ bits would cause
> corruption.
Yes, that's already true. I'm pointing out that if we depend on the
vismap for all-frozen, then losing bits *also* causes corruption, so
that's something we need to test for. Right now, there is no possible
corruption from losing bits; we simply end up scannning more pages than
we have to.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-05-31 18:05:36 | Re: removing PD_ALL_VISIBLE |
| Previous Message | Alexander Korotkov | 2013-05-31 17:53:04 | Re: Behavior of a pg_trgm index for 2 (or < 3) character LIKE queries |