Re: pg_config --version

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_config --version
Date: 2016-11-27 06:16:37
Message-ID: CAB7nPqQ5D6WYp2dWunSsvFT+kYcpsrBHZPZyU51DdvervSN+eQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Nov 27, 2016 at 9:16 AM, David Fetter <david(at)fetter(dot)org> wrote:
> While updating some extensions, I noticed that pg_config --version
> produces output that's...maybe not quite as useful as it might be, at
> least to a machine, so I'd like to throw out some proposals to fix the
> situation.
>
> Add a --version-numeric option to pg_config
>
> or
> Replace the current --version option with its bare numeric version
>
> or
> Add another line of output to the current --version output, which
> would be the numeric version by itself
>
> What say?

You may want to look at this thread that treats more or less the same topic:
https://www.postgresql.org/message-id/CAB7nPqTAdAJpX8iK4V3uYJbO2Kmo8rHzqJKDsLaDdranNrGX_A@mail.gmail.com
And this has resulted in commit a5d489cc:
commit: a5d489ccb7e613c7ca3be6141092b8c1d2c13fa7
author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
date: Thu, 2 Jul 2015 17:24:36 -0400
Make numeric form of PG version number readily available in Makefiles.

I would imagine that the common position has not changed much since,
and as Makefile.global.in provides this data... Doing more work in
pg_config is not really necessary for extensions.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amos Bird 2016-11-27 08:01:05 Re: make default TABLESPACE belong to target table.
Previous Message Amit Kapila 2016-11-27 03:49:06 Re: UNDO and in-place update