Message-ID: <0766030b47d9c46484c7ae8569a4e5b97b58b43d.camel@j-davis.com>
Subject: Re: pgsql: Re-validate connection string in libpqrcv_connect().
From: Jeff Davis <pgsql@j-davis.com>
To: Jeff Davis <jdavis@postgresql.org>, pgsql-committers@lists.postgresql.org
Cc: vignesh C <vignesh21@gmail.com>
Date: Fri, 12 Jan 2024 23:02:45 -0800
In-Reply-To: <E1rOPIq-001842-VG@gemulon.postgresql.org>
References: <E1rOPIq-001842-VG@gemulon.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4-0ubuntu2 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/0766030b47d9c46484c7ae8569a4e5b97b58b43d.camel%40j-davis.com>
Precedence: bulk

On Fri, 2024-01-12 at 21:43 +0000, Jeff Davis wrote:
> Re-validate connection string in libpqrcv_connect().

Looks like the test is causing problems on drogo:

ERROR:  could not connect to the publisher: connection to server at
"127.0.0.1", port 54707 failed: FATAL:  SSPI authentication failed for
user "regress_test_user"'

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Ddrongo&dt=3D2024-=
01-13%2002%3A41%3A35

I think we need to change the pg_hba.conf on the publisher before
creating (or at least before enabling) the subscription. I might have
to commit a trial fix unless someone can debug this more easily on
drogo's configuration.

I suppose I could also take out the test, but I like that it adds
better coverage of the password_required setting.

Regards,
	Jeff Davis