Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pFGGJ-0008W8-TD for pgsql-bugs@arkaria.postgresql.org; Tue, 10 Jan 2023 15:10:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pFGGI-0007zB-SR for pgsql-bugs@arkaria.postgresql.org; Tue, 10 Jan 2023 15:10:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pFGGI-0007z2-KS for pgsql-bugs@lists.postgresql.org; Tue, 10 Jan 2023 15:10:02 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pFGGC-0000vS-85 for pgsql-bugs@lists.postgresql.org; Tue, 10 Jan 2023 15:10:01 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 30AF9snT265455; Tue, 10 Jan 2023 10:09:54 -0500 From: Tom Lane To: Anbazhagan M cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17740: Connecting postgresql 13 with different psql versions In-reply-to: References: <17740-f9e629897b58b2c3@postgresql.org> <4092738.1673277565@sss.pgh.pa.us> <4115647.1673283004@sss.pgh.pa.us> Comments: In-reply-to Anbazhagan M message dated "Tue, 10 Jan 2023 19:32:08 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <265453.1673363394.1@sss.pgh.pa.us> Date: Tue, 10 Jan 2023 10:09:54 -0500 Message-ID: <265454.1673363394@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Anbazhagan M writes: > If psql v11 is behaving in a right way, what difference made psql v13 to > behave in a different way ? Was there any changes done between versions of > psql v11 and v13 ? I told you already: I think the relevant difference is the addition of GSS (i.e. Kerberos or equivalent) support starting in v12. Both versions are behaving correctly according to their own feature sets. What is missing is that you need to update your pg_hba.conf to account for the possibility of GSS-encrypted connections. regards, tom lane