RFC: Add 'taint' field to pg_control.

Поиск
Список
Период
Сортировка
От Andres Freund
Тема RFC: Add 'taint' field to pg_control.
Дата
Msg-id 20180228214311.jclah37cwh572t2c@alap3.anarazel.de
обсуждение исходный текст
Ответы Re: RFC: Add 'taint' field to pg_control.  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Re: RFC: Add 'taint' field to pg_control.  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Re: RFC: Add 'taint' field to pg_control.  (Justin Pryzby <pryzby@telsasoft.com>)
Re: RFC: Add 'taint' field to pg_control.  (Craig Ringer <craig@2ndquadrant.com>)
Список pgsql-hackers
Hi,

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
'cluster_history'.

Greetings,

Andres Freund


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Darafei Praliaskouski
Дата:
Сообщение: Re: Cast jsonb to numeric, int, float, bool
Следующее
От: Nikita Glukhov
Дата:
Сообщение: Re: [HACKERS] [PATCH] kNN for SP-GiST