From: | Anbazhagan M <gopi(dot)anbumech(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17740: Connecting postgresql 13 with different psql versions |
Date: | 2023-01-10 14:02:08 |
Message-ID: | CA+SbrTdjEVfb8WXQZFkhSVWMXpe1bQeKx2=nkDDREO1xQk=qiA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)anbumech(at)gmail(dot)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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Anbazhagan M <gopi(dot)anbumech(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jeffrey Walton | 2023-01-10 14:42:03 | [OT] Microsoft: Kubernetes clusters hacked in malware campaign via PostgreSQL |
Previous Message | James Pang (chaolpan) | 2023-01-10 13:41:34 | pg_logical_slot_peek_changes with slots created with pglogical_output missed DML records, |