pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: jian xu <jamesxu@outlook.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: pg13 psql can't connect pg instance with ssl enabled after upgrading
Date: Fri, 12 Feb 2021 17:59:46 -0500
Message-ID: <1611195.1613170786@sss.pgh.pa.us> (raw)
In-Reply-To: <BL0PR02MB45612EA590D8ACB9A14A0E7BA18B9@BL0PR02MB4561.namprd02.prod.outlook.com>
References: <BL0PR02MB456168A5C9909C71C578CFFDA18B9@BL0PR02MB4561.namprd02.prod.outlook.com>
	<1608034.1613166623@sss.pgh.pa.us>
	<BL0PR02MB45612EA590D8ACB9A14A0E7BA18B9@BL0PR02MB4561.namprd02.prod.outlook.com>

jian xu <jamesxu@outlook.com> writes:
> Thanks Tom.  you are right, we are using GSS authentication. and psql version is 13.1
> postgresql_13_1/bin/psql --version
> psql (PostgreSQL) 13.1

Ah.  Then perhaps you want hostgssenc not hostssl in your pg_hba
entries.  But I'd definitely recommend an update to 13.2, as it
fixes a number of GSS bugs besides this one.

			regards, tom lane

view thread (6+ messages)  latest in thread

Message-ID: <1611195.1613170786@sss.pgh.pa.us>
Permalink:  ../1611195.1613170786@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1611195.1613170786@sss.pgh.pa.us

copy link · copy postgr.es

reply

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-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jamesxu@outlook.com
  Subject: Re: pg13 psql can't connect pg instance with ssl enabled after upgrading
  In-Reply-To: <1611195.1613170786@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