From: Tom Lane <tgl@sss.pgh.pa.us>
To: nuko.yokohama@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18685: .pgpass is not enabled when running pg_basebackup on PostgreSQL 17.
Date: Mon, 04 Nov 2024 14:40:23 -0500
Message-ID: <2887158.1730749223@sss.pgh.pa.us> (raw)
In-Reply-To: <18685-fee2dd142b9688f1@postgresql.org>
References: <18685-fee2dd142b9688f1@postgresql.org>
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: tgl@sss.pgh.pa.us, nuko.yokohama@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18685: .pgpass is not enabled when running pg_basebackup on PostgreSQL 17.
In-Reply-To: <2887158.1730749223@sss.pgh.pa.us>
* 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