Re: Sigh, we need an initdb - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Sigh, we need an initdb
Date
Msg-id 16641.1401924506@sss.pgh.pa.us
Whole thread Raw
In response to Re: Sigh, we need an initdb  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> I think that's worth considering.  Another idea is: suppose we set up
>> a PostgreSQL database somewhere that contained information about what
>> controldata layout corresponded to what control version:

> That seems possibly workable.

BTW, a possibly-easier-to-implement idea is to git diff pg_control.h
against the previous release branch.  Any non-comment diffs (or, really,
anything at all except a copyright date change) should excite a warning
unless a change to the PG_CONTROL_VERSION line is included.  We'd probably
need a way to shut it up after a simple comment change, but otherwise
not a lot of infrastructure needed except a shell script.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: btree_gist valgrind warnings about uninitialized memory
Next
From: Tom Lane
Date:
Subject: Re: btree_gist valgrind warnings about uninitialized memory