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

From Andrew Gierth
Subject Re: Exposing PG_VERSION_NUM in pg_config
Date
Msg-id 87mw2sxt6j.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: Exposing PG_VERSION_NUM in pg_config  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Exposing PG_VERSION_NUM in pg_config
List pgsql-hackers
>>>>> "Michael" == Michael Paquier <michael.paquier@gmail.com> writes:
Michael> For an extension that has a single branch compatible with aMichael> set of multiple major versions of
Postgres,the cases areMichael> custom values for REGRESS_OPTS and REGRESS depending on theMichael> backend version. I
alsomanipulate on a daily basis the sameMichael> set of scripts across many platforms (on Windows as well usingMichael>
msysgit,and MSVC installation does not have pgxs stuff), so IMichael> would use it to simplify them. It is true that
youcan alreadyMichael> do that by parsing the output of "pg_config --version",
 

What _exactly_ would you be doing that you could not already do better
with $(MAJORVERSION) which is already defined in Makefile.global?

-- 
Andrew (irc:RhodiumToad)



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );
Next
From: Vladimir Borodin
Date:
Subject: Re: Vacuuming big btree indexes without pages with deleted items