Re: BUG #17740: Connecting postgresql 13 with different psql versions - Mailing list pgsql-bugs

From Anbazhagan M
Subject Re: BUG #17740: Connecting postgresql 13 with different psql versions
Date
Msg-id CA+SbrTdjEVfb8WXQZFkhSVWMXpe1bQeKx2=nkDDREO1xQk=qiA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17740: Connecting postgresql 13 with different psql versions  (Anbazhagan M <gopi.anbumech@gmail.com>)
Responses Re: BUG #17740: Connecting postgresql 13 with different psql versions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Dear Tom Lane/ Team,

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 ?
Is it possible not to skip the gss auth line as it was in psql v11 ? 

Sample pg_hba as in my original post is as below,

local all pgbkp peer map=pgbackrest
hostssl all +pg_app_read 0.0.0.0/0 gss map=krb
host all all 0.0.0.0/0 scram-sha-256



On Mon, 9 Jan 2023 at 23:00, Anbazhagan M <gopi.anbumech@gmail.com> wrote:
Thanks a lot Tom Lane. 
Can you please help with documentation on how to use hostgssenc....reject? 


On Mon, 9 Jan, 2023, 10:20 pm Tom Lane, <tgl@sss.pgh.pa.us> wrote:
Anbazhagan M <gopi.anbumech@gmail.com> writes:
> Any workaround is there for this to make it work as it was when pg 13 was
> connected with psql v11?

You could add a hostgssenc line specifying what you want the server
to do with that --- maybe just "hostgssenc ... reject" if you don't
want to think hard about it.

                        regards, tom lane


--
Regards,
Anbu 

pgsql-bugs by date:

Previous
From: "James Pang (chaolpan)"
Date:
Subject: pg_logical_slot_peek_changes with slots created with pglogical_output missed DML records,
Next
From: Jeffrey Walton
Date:
Subject: [OT] Microsoft: Kubernetes clusters hacked in malware campaign via PostgreSQL