Message-ID: <d48d874f3dbdb7b0ae749f0644baaf95f48a4929.camel@cybertec.at>
Subject: Re: BUG #18685:  -> Does the similar bug affect executable
 "pg_dump" too in Ver 17.0
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Bharani SV-forum <esteembsv-forum@yahoo.com>, "nuko.yokohama@gmail.com"
	 <nuko.yokohama@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: Tue, 05 Nov 2024 18:06:24 +0100
In-Reply-To: <749602451.2951310.1730823617713@mail.yahoo.com>
References: <18685-fee2dd142b9688f1@postgresql.org>
	 <2887158.1730749223@sss.pgh.pa.us>
	 <749602451.2951310.1730823617713@mail.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.52.4 (3.52.4-2.fc40) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/d48d874f3dbdb7b0ae749f0644baaf95f48a4929.camel%40cybertec.at>
Precedence: bulk

On Tue, 2024-11-05 at 16:20 +0000, Bharani SV-forum wrote:
> Does the similar bug affect,=C2=A0 executable "pg_dump" too in Ver 17.0

According to the commit message https://postgr.es/c/e2a9129093
pg_dump is not affected.

> On Monday, November 4, 2024 at 02:40:34 PM EST, Tom Lane <tgl@sss.pgh.pa.=
us> wrote:=20
>=20
> PG Bug reporting form <noreply@postgresql.org> writes:
>=20
> > In PostgreSQL 16, pg_basebackup could be run without prompting for a
> > password.
> > However, when running pg_basebacup on PostgreSQL 17, the user is prompt=
ed
> > for a password even if .pgpass is set.
>=20
>=20
> Yup, that's a bug.=C2=A0 Fix pushed, thanks for the report!

Yours,
Laurenz Albe