Re: WIP checksums patch - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: WIP checksums patch
Date
Msg-id 1349113246.15580.63.camel@jdavis
Whole thread Raw
In response to Re: WIP checksums patch  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: WIP checksums patch  (Amit Kapila <amit.kapila@huawei.com>)
List pgsql-hackers
On Mon, 2012-10-01 at 18:14 +0100, Simon Riggs wrote:
> You are missing large parts of the previous thread, giving various
> opinions on what the UI should look like for enabling checksums.

I read through all of the discussion that I could find. There was quite
a lot, so perhaps I have forgotten pieces of it.

But that one section in the docs does look out of date and/or confusing
to me.

I remember there was discussion about a way to ensure that checksums are
set cluster-wide with some kind of special command (perhaps related to
VACUUM) and a magic file to let recovery know whether checksums are set
everywhere or not. That doesn't necessarily conflict with the GUC though
(the GUC could be a way to write checksums lazily, while this new
command could be a way to write checksums eagerly).

If some consensus was reached on the exact user interface, can you
please send me a link?

Regards,Jeff Davis





pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: WIP checksums patch
Next
From: Dariel Nicolas De Jesus Medrnao
Date:
Subject: Installation of xpath (read xml on postgres)