Re: pg_basebackup: Always return valid temporary slot names

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Nishant Sharma <nishant(dot)sharma(at)enterprisedb(dot)com>
Cc: Jelte Fennema <me(at)jeltef(dot)nl>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
Subject: Re: pg_basebackup: Always return valid temporary slot names
Date: 2023-09-05 09:39:26
Message-ID: FC948CB3-798E-419C-9910-4B865348DD78@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 5 Sep 2023, at 09:09, Nishant Sharma <nishant(dot)sharma(at)enterprisedb(dot)com> wrote:

> With this, I was thinking, isn't this a problem of pgbouncer filling
> be_pid with random bits? Maybe it should have filled the be_pid
> with a random positive integer instead of any integer as it
> represents a pid?

I'm inclined to agree that anyone sending a value which is supposed to
represent a PID should be expected to send a value which corresponds to the
format of a PID.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2023-09-05 09:59:40 Re: Optionally using a better backtrace library?
Previous Message Daniel Gustafsson 2023-09-05 09:35:02 Re: logfmt and application_context