pgsql: pg_basebackup: Generate valid temporary slot names under PQbacke - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: pg_basebackup: Generate valid temporary slot names under PQbacke
Date
Msg-id E1qe7KM-002lpB-Ce@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
pg_basebackup: Generate valid temporary slot names under PQbackendPID()

pgbouncer can cause PQbackendPID() to return negative values due to it
filling be_pid with random bytes (even these days pid_max can only be
set up to 2^22 on 64b machines on Linux, for example, so this cannot
happen with normal PID numbers).  When this happens, pg_basebackup may
generate a temporary slot name that may not be accepted by the parser,
leading to spurious failures, like:
pg_basebackup: error: could not send replication command
ERROR:  replication slot name "pg_basebackup_-1201966863" contains
invalid character

This commit fixes that problem by formatting the result from
PQbackendPID() as an unsigned integer when creating the temporary
replication slot name, so as the invalid character is gone and the
command can be parsed.

Author: Jelte Fennema
Reviewed-by: Daniel Gustafsson, Nishant Sharma
Discussion: https://postgr.es/m/CAGECzQQOGvYfp8ziF4fWQ_o8s2K7ppaoWBQnTmdakn3s-4Z=5g@mail.gmail.com
Backpatch-through: 11

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/9de74ca706f64ff44bac7ba54209dd1a6eabdb45

Modified Files
--------------
src/bin/pg_basebackup/pg_basebackup.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Thomas Munro
Date:
Subject: pgsql: Fix instability in 031_recovery_conflict.pl.
Next
From: Alvaro Herrera
Date:
Subject: pgsql: Update information_schema definition for not-null constraints