Re: Exposing PG_VERSION_NUM in pg_config - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Exposing PG_VERSION_NUM in pg_config
Date
Msg-id CAB7nPqS0pq2OZAE=3vvOkC3snQAny5k9Umvt9XOR=61wqr=haA@mail.gmail.com
Whole thread
In response to Re: Exposing PG_VERSION_NUM in pg_config  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Exposing PG_VERSION_NUM in pg_config
Re: Exposing PG_VERSION_NUM in pg_config
List pgsql-hackers


On Tue, Mar 31, 2015 at 5:39 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
On 3/25/15 1:32 AM, Michael Paquier wrote:
> Well, I have no other cases than ones of the type mentioned upthread,
> and honestly I am fine as long as we do not apply maths to a version
> string. So attached is a patch that adds VERSION_NUM in
> Makefile.global.

How would you make use of this in an extension makefile?

One use case is regression test list filtering depending on backend version.
--
Michael

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Vacuuming big btree indexes without pages with deleted items
Next
From: Jim Nasby
Date:
Subject: Re: Bug fix for missing years in make_date()