From: Bharani SV-forum <esteembsv-forum@yahoo.com>
To: nuko.yokohama@gmail.com <nuko.yokohama@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Cc: Bharani SV esteembsv-forum <esteembsv-forum@yahoo.com>
Subject: BUG #18685: -> Does the similar bug affect executable "pg_dump" too in Ver 17.0
Date: Tue, 5 Nov 2024 16:20:17 +0000 (UTC)
Message-ID: <749602451.2951310.1730823617713@mail.yahoo.com> (raw)
In-Reply-To: <2887158.1730749223@sss.pgh.pa.us>
References: <18685-fee2dd142b9688f1@postgresql.org>
<2887158.1730749223@sss.pgh.pa.us>
TeamDoes the similar bug affect, executable "pg_dump" too in Ver 17.0
Please confirm
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!
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: esteembsv-forum@yahoo.com, nuko.yokohama@gmail.com, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18685: -> Does the similar bug affect executable "pg_dump" too in Ver 17.0
In-Reply-To: <749602451.2951310.1730823617713@mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox