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

From Justin Pryzby
Subject Re: RFC: Add 'taint' field to pg_control.
Date
Msg-id 20200323182143.GA17348@telsasoft.com
Whole thread Raw
In response to Re: RFC: Add 'taint' field to pg_control.  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
On Wed, Feb 28, 2018 at 04:16:53PM -0600, Justin Pryzby wrote:
> On Wed, Feb 28, 2018 at 01:43:11PM -0800, Andres Freund wrote:
> > a significant number of times during investigations of bugs I wondered
> > whether running the cluster with various settings, or various tools
> > could've caused the issue at hand.  Therefore I'd like to propose adding
> > a 'tainted' field to pg_control, that contains some of the "history" of
> > the cluster. Individual bits inside that field that I can think of right
> > now are:
> > - pg_resetxlog was used non-passively on cluster
> > - ran with fsync=off
> > - ran with full_page_writes=off
> > - pg_upgrade was used

+ cluster was downgraded (between minor releases)

Dregging up a years old thread since I thought that was worth adding..

-- 
Justin



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Assert() failures during RI checks
Next
From: "Daniel Verite"
Date:
Subject: Re: Making psql error out on output failures