From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Add port/strnlen support to libpq and ecpg Makefiles. |
Date: | 2017-10-11 16:12:18 |
Message-ID: | 20171011161218.xnnedpo47qa2voi6@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Hi,
On 2017-10-11 11:58:58 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > Phew. This is a bit a sad state of affairs. The separate libpq logic for
> > getting pgport is presumably because of possibly different threading
> > flags and then because of the appropriate compiler/linker flags for a
> > shared library?
>
> I don't see why threading would matter, but building with -fPIC or
> not is definitely an issue.
-pthread changes some "memory model" type assumptions by the compiler
too IIRC, not just linker stage things. In a non-threaded environment
the compiler is kinda free to invent phantom stores and such. It's
unlikely to matter for just pgbench, but ...
> I agree the PITA factor of the current approach keeps increasing.
> It sounds a bit silly to build libpgport three ways, but maybe
> we should just do that.
We already kinda are, just by copying things around ;)
> Or conceivably we should just build the FE version of libpgport.a
> with -fPIC and not worry about whether that loses some efficiency
> for client programs. A lot of distros are effectively forcing
> that, or even -fPIE, anyway.
Hm.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-10-11 16:32:20 | Re: [COMMITTERS] pgsql: Add port/strnlen support to libpq and ecpg Makefiles. |
Previous Message | Tom Lane | 2017-10-11 15:58:58 | Re: pgsql: Add port/strnlen support to libpq and ecpg Makefiles. |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-10-11 16:27:51 | Re: Predicate Locks for writes? |
Previous Message | Alvaro Herrera | 2017-10-11 16:05:32 | Re: SendRowDescriptionMessage() is slow for queries with a lot of columns |