On 01/05/2018 09:36 PM, Travis Allison wrote:
Tom, I guess I don't understand the point of having a different
pg_config.h in my user/include/postgresql directory than the postgresql
server that I am running. You mentioned building client code that would
reference the pg_config.h in user/include/postgresql. A couple of
questions:
What type of client code are you referring to?
What is the point of having a pg_config.h for a server that I am not
even running?
Not Tom, but to answer:
As to client code, that would include the Postgres CLI client psql or
the Python adapter psycopg2 among others. This code does not need to be
on the server machine, it can be anywhere you want a client to connect
to a Postgres server.
The point of a more recent pg_config.h is that client code compiled with
it would be backwards compatible whereas compiling against an older
version would result in code that would not work against newer servers.
The problem you are running into is that the build process is using both
the older(9.6.5) and newer(10.0) pg_config.h at the same time.
Travis
On Fri, Jan 5, 2018 at 8:05 PM, Tom Lane <tgl@xxxxxxxxxxxxx
<mailto:tgl@xxxxxxxxxxxxx>> wrote:
Travis Allison <travisallison@xxxxxxxxx
<mailto:travisallison@xxxxxxxxx>> writes:
> I suppose an easy workaround is to copy my version 9.6 pg_config.h into my
> user/include/postgresql directory and replace the one installed by
> libpq-dev.
> Can you think of any detrimental side-effects from doing that?
I would not recommend that: it's likely to break code that's expecting
the Ubuntu-standard layout. I think your best course is to adapt the
particular package you're having trouble with to work with that layout.
Maybe contact its author for help?
regards, tom lane
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
