Horton

Re: BUG #18685: -> Does the similar bug affect executable "pg_dump" too in Ver 17.0

Laurenz Albe <laurenz.albe@cybertec.at>

View thread View on postgr.es
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: 2024-11-05T17:06:24Z
Lists: pgsql-bugs 
On Tue, 2024-11-05 at 16:20 +0000, Bharani SV-forum wrote:
> Does the similar bug affect,  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: 
> 
> PG Bug reporting form <noreply@postgresql.org> writes:
> 
> > In PostgreSQL 16, pg_basebackup could be run without prompting for a
> > password.
> > However, when running pg_basebacup on PostgreSQL 17, the user is prompted
> > for a password even if .pgpass is set.
> 
> 
> Yup, that's a bug.  Fix pushed, thanks for the report!

Yours,
Laurenz Albe

Commits

  1. pg_basebackup, pg_receivewal: fix failure to find password in ~/.pgpass.