Re: Build issue with postgresql 17 undefined reference to `pg_encoding_to_char' and `pg_char_to_encoding'

Mikael Sand <msand@seaber.io> writes:
> I wonder if it would be possible to link pgcommon_shlib and pgport_shlib
> statically into pq and do LTO already at that point, such that consumers of
> libpq could merely link against libpq.a and that would be enough?

What would be the point?  A typical build will still have a pile of
outside dependencies that static-link consumers will have to track
manually (openssl and so forth).  So I don't see how this'd move
the needle much.

            regards, tom lane