Re: How to declare PG version for compiling extensions.

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: GPT <gptmailinglists(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How to declare PG version for compiling extensions.
Date: 2018-10-23 09:17:43
Message-ID: 8736sx81vk.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>>>> "GPT" == GPT <gptmailinglists(at)gmail(dot)com> writes:

GPT> Unfortunately, I had not installed the following package:
GPT> "postgresql-server-dev-11"

GPT> By the way, shouldn't a warning message appear while trying to run:

GPT> `PATH=/usr/lib/postgresql/11/bin:$PATH make USE_PGXS=1`

GPT> warning the user that some files are missing.

It's more reliable to do (if the makefile is correctly written):

make USE_PGXS=1 PG_CONFIG=/usr/lib/postgresql/11/bin/pg_config

By specifying the pg_config binary explicitly rather than relying on the
PATH, you avoid the chance of picking up an incorrect copy by mistake.
This is why the standard form for pgxs makefiles has an assignment for
PG_CONFIG before the PGXS assignment line; the command-line option
overrides it.

--
Andrew (irc:RhodiumToad)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Lutz Horn 2018-10-23 09:38:01 Select "todays" timestamps in an index friendly way
Previous Message Boris Sagadin 2018-10-23 05:28:27 Re: Postgres 10, slave not catching up with master