From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: RFC: Add 'taint' field to pg_control. |
Date: | 2020-03-23 18:21:43 |
Message-ID: | 20200323182143.GA17348@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2020-03-23 18:51:57 | Re: Making psql error out on output failures |
Previous Message | Tom Lane | 2020-03-23 17:54:31 | Re: Assert() failures during RI checks |