postgres.git / summary / log / commit / refs

commit    cfd7aadebea1997e26cb96f31f8eb9af95affa36
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Tue Jan 14 23:50:24 2025 +0000
First released in: 18.0, 13.19, 14.16, 15.11, 16.7, 17.3

    Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c.
    
    In the name of ABI stability (that is, to avoid a library major
    version bump for libpq), libpq still exports a version of pqsignal()
    that we no longer want to use ourselves.  However, since that has
    the same link name as the function exported by src/port/pqsignal.c,
    there is a link ordering dependency determining which version will
    actually get used by code that uses libpq as well as libpgport.a.
    
    It now emerges that the wrong version has been used by pgbench and
    psql since commit 06843df4a rearranged their link commands.  This
    can result in odd failures in pgbench with the -T switch, since its
    SIGALRM handler will now not be marked SA_RESTART.  psql may have
    some edge-case problems in \watch, too.
    
    Since we don't want to depend on link ordering effects anymore,
    let's fix this in the same spirit as b6c7cfac8: use macros to change
    the actual link names of the competing functions.  We cannot change
    legacy-pqsignal.c's exported name of course, so the victim has to be
    src/port/pqsignal.c.
    
    In master, rename its exported name to be pqsignal_fe in frontend or
    pqsignal_be in backend.  (We could perhaps have gotten away with using
    the same symbol in both cases, but since the FE and BE versions now
    work a little differently, it seems advisable to use different names.)
    
    In back branches, rename to pqsignal_fe in frontend but keep it as
    pqsignal in backend.  The frontend change could affect third-party
    code that is calling pqsignal from libpgport.a or libpgport_shlib.a,
    but only if the code is compiled against port.h from a different minor
    release than libpgport.  Since we don't support using libpgport as a
    shared library, it seems unlikely that there will be such a problem.
    I left the backend symbol unchanged to avoid an ABI break for
    extensions.  This means that the link ordering hazard still exists
    for any extension that links against libpq.  However, none of our own
    extensions use both pqsignal() and libpq, and we're not making things
    any worse for third-party extensions that do.
    
    Report from Andy Fan, diagnosis by Fujii Masao, patch by me.
    Back-patch to all supported branches, as 06843df4a was.
    
    Discussion: https://postgr.es/m/87msfz5qv2.fsf@163.com


src/include/port.h | 5 ++++- src/interfaces/libpq/legacy-pqsignal.c | 12 +++++++++--- src/port/pqsignal.c | 4 ++++ 3 files changed, 17 insertions(+), 4 deletions(-) diff --git a/src/include/port.h b/src/include/port.h index 6e21f6e0907..e8b7a35be6e 100644 --- a/src/include/port.h +++ b/src/include/port.h @@ -550,7 +550,10 @@ extern int pg_check_dir(const char *dir); /* port/pgmkdirp.c */ extern int pg_mkdir_p(char *path, int omode); -/* port/pqsignal.c */ +/* port/pqsignal.c (see also interfaces/libpq/legacy-pqsignal.c) */ +#ifdef FRONTEND +#define pqsignal pqsignal_fe +#endif typedef void (*pqsigfunc) (int signo); extern pqsigfunc pqsignal(int signo, pqsigfunc func); diff --git a/src/interfaces/libpq/legacy-pqsignal.c b/src/interfaces/libpq/legacy-pqsignal.c index 4703adbf0cc..de5f8963588 100644 --- a/src/interfaces/libpq/legacy-pqsignal.c +++ b/src/interfaces/libpq/legacy-pqsignal.c @@ -28,10 +28,16 @@ * with the semantics it had in 9.2; in particular, this has different * behavior for SIGALRM than the version in src/port/pqsignal.c. * - * libpq itself uses this only for SIGPIPE (and even then, only in - * non-ENABLE_THREAD_SAFETY builds), so the incompatibility isn't - * troublesome for internal references. + * libpq itself does not use this, nor does anything else in our code. + * + * src/include/port.h will #define pqsignal as pqsignal_fe, + * but here we want to export just plain "pqsignal". We can't rely on + * port.h's extern declaration either. (The point of that #define + * is to ensure that no in-tree code accidentally calls this version.) */ +#undef pqsignal +extern pqsigfunc pqsignal(int signo, pqsigfunc func); + pqsigfunc pqsignal(int signo, pqsigfunc func) { diff --git a/src/port/pqsignal.c b/src/port/pqsignal.c index 9bd0068d9a7..215df56bda2 100644 --- a/src/port/pqsignal.c +++ b/src/port/pqsignal.c @@ -35,6 +35,10 @@ * Set up a signal handler, with SA_RESTART, for signal "signo" * * Returns the previous handler. + * + * Note: the actual name of this function is either pqsignal_fe when + * compiled with -DFRONTEND, or pqsignal when compiled without that. + * This is to avoid a name collision with libpq's legacy-pqsignal.c. */ pqsigfunc pqsignal(int signo, pqsigfunc func) [parent: f217c410553d]