information, and I don't like it
when such information is merely implied.
--
Florian Weimer<[EMAIL PROTECTED]>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
--
+ not the system crashes at the same time.
+
I think fsync=off also endagers metadata, while synchronous_commit=off
should be perfectly safe as far as the metadata is concerned.
Wouldn't this be worth mentioning as well?
--
Florian Weimer<[EMAIL PROTECTED]&
* Tom Lane:
> I think short burst errors are fairly likely: the kind of scenario I'm
> worried about is a wild store corrupting a word of a WAL entry while
> it's waiting around to be written in the WAL buffers.
Ah, does this mean that each WAL entry gets its own checksum? In this
case, Adler32
* Tom Lane:
> Florian Weimer <[EMAIL PROTECTED]> writes:
>> Have you tried switching to Adler32 instead of CRC32?
>
> Is anything known about the error detection capabilities of Adler32?
> There's a lot of math behind CRCs but AFAIR Adler's method is pretty
>
* Simon Riggs:
>> Surely not. Otherwise even the "on" setting is not really a defense.
>
> Only when the CRC is exactly zero, which happens very very rarely.
Have you tried switching to Adler32 instead of CRC32?
--
Florian Weimer<[EMAIL PROTECTED]
