RFC: Add 'taint' field to pg_control.

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Subject: RFC: Add 'taint' field to pg_control.
Date: 2018-02-28 21:43:11
Message-ID: 20180228214311.jclah37cwh572t2c@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers


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

What do others think?

Perhaps we should rename 'tainted' to something less "blame-y" sounding,
but I can't quite think of something more descriptive than


Andres Freund


Browse pgsql-hackers by date

  From Date Subject
Next Message Nikita Glukhov 2018-02-28 21:58:42 Re: [HACKERS] [PATCH] kNN for SP-GiST
Previous Message Darafei Praliaskouski 2018-02-28 21:43:08 Re: Cast jsonb to numeric, int, float, bool