From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Adding optionally commit number in PG_VERSION_STR |
Date: | 2013-07-17 01:55:41 |
Message-ID: | CAB7nPqQqu72r-kQTtADecT0DtciAfmKFnS=+OcoLMP5MYj=8xg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all,
It happens that I work occasionally on multiple builds based on
different stable branches at the same time to check fixes that need to
be backpatched, and I tend to easily lose track on which version the
build I created is based on (Duh!). There is of course the version
number up to the 3rd digit available (for example 9.2.4, 9.3beta2,
etc.), but as a developer I think that it would be helpful to include
the commit ID in PG_VERSION_STR to get a better reference on exactly
what the development build is based on. This could be controlled by an
additional flag in ./configure.in called something like
--enable-version-commit, of course disabled by default. If enabled,
PG_VERSION_STR would be generated with the new information. configure
would also return an error when this flag is enabled if git is either
not found, or if the repository where configure is not a native git
repository.
Thoughts?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Karlsson | 2013-07-17 02:16:00 | Re: Listen/notify across clusters |
Previous Message | Noah Misch | 2013-07-17 00:31:15 | Re: Re: FILTER for aggregates [was Re: Department of Redundancy Department: makeNode(FuncCall) division] |