Re: [HACKERS] Adding optionally commit number in PG_VERSION_STR

2013-07-17 Thread Michael Paquier
On Wed, Jul 17, 2013 at 5:20 PM, Dave Page wrote: > On Wed, Jul 17, 2013 at 2:55 AM, Michael Paquier > wrote: >> 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

Re: [HACKERS] Adding optionally commit number in PG_VERSION_STR

2013-07-17 Thread Dave Page
On Wed, Jul 17, 2013 at 2:55 AM, Michael Paquier wrote: > 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

Re: [HACKERS] Adding optionally commit number in PG_VERSION_STR

2013-07-16 Thread Erik Rijkers
On Wed, July 17, 2013 05:27, Tom Lane wrote: > Michael Paquier writes: >> It happens that I work occasionally on multiple builds based on FWIW, I've been doing this for while: where $project is mostly the patchname, $commit_hash is extracted like this: commit_hash=$( cd /home/aardvark/pg_stuf

Re: [HACKERS] Adding optionally commit number in PG_VERSION_STR

2013-07-16 Thread Tom Lane
Michael Paquier writes: > 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 ver

[HACKERS] Adding optionally commit number in PG_VERSION_STR

2013-07-16 Thread Michael Paquier
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 3r