Re: PostgreSQL always uses own versions of *printf(), but does not export them

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Patrik Novotny <panovotn(at)redhat(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL always uses own versions of *printf(), but does not export them
Date: 2020-06-23 14:14:10
Message-ID: 2148682.1592921650@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Patrik Novotny <panovotn(at)redhat(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Hardik Bansal 2020-06-23 23:06:36 Very slow inserts when using postgres_fdw + declarative partitioning
Previous Message Aetimpani Yeatina 2020-06-23 14:00:45 Stranger Character Input Bug