Message-ID: <89f3ec586ade0b6fec211ea22d45fb32500611ff.camel@cybertec.at>
Subject: Re: pgpass file in postresql.auto.conf?
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: "Dan Mahoney (Gushi)" <postgres@gushi.org>, 
	pgsql-general@lists.postgresql.org
Date: Fri, 26 Sep 2025 16:17:44 +0200
In-Reply-To: <31ded2b6-d8f8-497c-59ea-c7885b4a7d26@gushi.org>
References: <31ded2b6-d8f8-497c-59ea-c7885b4a7d26@gushi.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-2.fc42) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/89f3ec586ade0b6fec211ea22d45fb32500611ff.camel%40cybertec.at>
Precedence: bulk

On Fri, 2025-09-26 at 12:05 +0000, Dan Mahoney (Gushi) wrote:
> In the interest of automation, I've set up a pgpass file for my=20
> pg_basebackup between master and standby.  This all works, thusly:
>=20
> pg_basebackup -d=20
> 'postgres://repuser@10.1.1.1:5432/foo?sslmode=3Dverify-ca' -F p=20
> --wal-method=3Dstream -P -R -D /var/db/postgres/data17-test3
>=20
> However, instead of the password getting baked into the pgsql.auto.conf,=
=20
> the reference to the passfile gets put in, instead:
>=20
> # Do not edit this file manually!
> # It will be overwritten by the ALTER SYSTEM command.
> primary_conninfo =3D 'user=3Drepuser passfile=3D''/var/db/postgres/.pgpas=
s''=20
> channel_binding=3Dprefer host=3D10.1.1.1 port=3D5432 sslmode=3D''verify-c=
a''=20
> sslnegotiation=3Dpostgres sslcompression=3D0 sslcertmode=3Dallow sslsni=
=3D1=20
> ssl_min_protocol_version=3DTLSv1.2 gssencmode=3Ddisable krbsrvname=3Dpost=
gres=20
> gssdelegation=3D0 target_session_attrs=3Dany load_balance_hosts=3Ddisable=
=20
> dbname=3Dfoo'

That happens when "pg_basebackup" used a password file to connect to
the PostgreSQL server.

> But it seems postgres won't actually read the passfile.

Oh yes, it will, as long as it has permissions 0600, 0400 or 0700 and
belongs to the database server OS user (commonly "postgres").
It must have worked for the "pg_basebackup", so PostgreSQL assumes it
will also work for replication.

> Sep 26 12:01:27 hostname postgres[42455]: [7-1] 2025-09-26 12:01:27.658=
=20
> UTC [42455] FATAL:  could not connect to the primary server: connection t=
o=20
> server at "10.1.1.1", port 5432 failed: fe_sendauth: no password supplied
>=20
> Am I doing something wrong here?

That is hard to say.  You should have run "pg_basebackup" as the
same OS user that starts the standby.

> I'm loathe to hand-edit the file, because of that warning there.

Makes sense, although it is OK as long as you don't mess up the file.


> Is there an alter system command that can be used to properly populate th=
e=20
> password into this file?

Sure.  If the standby server is up and running (even if it cannot connect
to the primary), you can connect and execute

  ALTER SYSTEM SET primary_conninfo =3D 'password=3D''my secret password'''=
;

Yours,
Laurenz Albe