Re: RFC: Add 'taint' field to pg_control. - Mailing list pgsql-hackers

From Andres Freund
Subject Re: RFC: Add 'taint' field to pg_control.
Date
Msg-id 20180228221812.mvk4h2rzxquqhbnr@alap3.anarazel.de
Whole thread Raw
In response to Re: RFC: Add 'taint' field to pg_control.  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: RFC: Add 'taint' field to pg_control.  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
Hi,

On 2018-02-28 17:14:18 -0500, Peter Eisentraut wrote:
> I can see why you'd want that, but as a DBA, I don't necessarily want
> all of that recorded, especially in a quasi-permanent way.

Huh?  You're arguing that we should make it easier for DBAs to hide
potential causes of corruption? I fail to see when that's necessary /
desirable? That a cluster ran with fsync=off isn't an embarassing thing,
nor does it contain private data...

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: RFC: Add 'taint' field to pg_control.
Next
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] MERGE SQL Statement for PG11