Re: Version defines

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: James William Pye <flaw(at)rhid(dot)com>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Version defines
Date: 2004-10-31 17:49:59
Message-ID: 28960.1099244999@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

James William Pye <flaw(at)rhid(dot)com> writes:
>> At compile time, you should be checking the specific feature you care
>> about,

> Well, for one of my uses, it is not a feature check. My PL loads a
> Python extension module whose path is dependent on the major and minor
> version of the PostgreSQL installation that the PL was compiled against.
> So I construct the module path string based on the major and minor at
> compile time.

Er ... can't you just keep it in pkglibdir and refer to it via $libdir?
Given that 8.0 now supports relocatable installations, I'd think it best
to avoid hardwiring any paths at compile time.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2004-10-31 18:02:09 Re: fsync, ext2 on Linux
Previous Message Tom Lane 2004-10-31 17:38:32 Re: make check error on -HEAD