On 2/28/18 16:43, 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
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. Maybe this could be stored in a separate location, like a small text/log-like file in the data directory. Then DBAs can save or keep or remove that information as they wish. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
