Re: libpq-fe.h should compile *entirely* standalone

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: libpq-fe.h should compile *entirely* standalone
Date: 2023-03-04 12:08:27
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2023-03-03 Fr 13:46, Tom Lane wrote:
> I wrote:
>> We can easily do better, as attached, but I wonder which other
>> headers should get the same treatment.
> After a bit of further research I propose the attached. I'm not
> sure exactly what subset of ECPG headers is meant to be exposed
> to clients, but we can adjust these patterns if new info emerges.
> This is actually moving the inclusion-check goalposts quite far,
> but HEAD seems to pass cleanly, and again we can always adjust later.
> Any objections?




Andrew Dunstan

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Kartyshov Ivan 2023-03-04 15:36:49 Re: [HACKERS] make async slave to wait for lsn to be replayed
Previous Message Drouvot, Bertrand 2023-03-04 11:19:57 Re: Minimal logical decoding on standbys