From: Tom Lane <tgl@sss.pgh.pa.us>
To: Patrik Novotny <panovotn@redhat.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: PostgreSQL always uses own versions of *printf(), but does not export them
Date: Tue, 23 Jun 2020 10:14:10 -0400
Message-ID: <2148682.1592921650@sss.pgh.pa.us> (raw)
In-Reply-To: <CAE_EZkhy0Sxm8Bnx3q4tBQakN4y--CQ-vDM24VNXXN83kVHgyA@mail.gmail.com>
References: <CAE_EZkhy0Sxm8Bnx3q4tBQakN4y--CQ-vDM24VNXXN83kVHgyA@mail.gmail.com>
Patrik Novotny <panovotn@redhat.com> writes:
> we came across an issue when compiling projects against PostgreSQL
> version >=12, as the *printf symbols seems not to be properly
> exported.
Possibly that external code is failing to link with libpgport?
We don't really support external code including our c.h ... but
anything that insists on doing so is very likely going to need
libpgport and/or libpgcommon.
But TBH I'd try to get rid of the inclusion, rather than let the
external code get further into bed with Postgres' internal
portability hacks. We never have, and we never will, promise
that c.h remains stable across PG versions.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, panovotn@redhat.com, pgsql-bugs@lists.postgresql.org
Subject: Re: PostgreSQL always uses own versions of *printf(), but does not export them
In-Reply-To: <2148682.1592921650@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox