Re: BUG #18358: I am not able to change the existing SQL connection to Postgres connection in existing application

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: noordeen(dot)sf3844(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18358: I am not able to change the existing SQL connection to Postgres connection in existing application
Date: 2024-02-22 10:15:41
Message-ID: 7982B9DF-AD23-49BB-8905-7617134BAE37@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 22 Feb 2024, at 06:25, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:

> Routine: ClientAuthentication 28000: no pg_hba.conf entry for host
> "10.136.66.234", user "doadmin", database "defaultdb", no encryption

> Can I have any solution to migrate from Microsoft SQL Server to Postgres
> SQL?

The error is fairly clear that Client Authentication failed when connecting,
that might be a good place to start investigating.

--
Daniel Gustafsson

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-02-22 14:43:18 BUG #18359: autovacuum stopped vacuuming user tables, focusing on just pg_auth_members repeatedly
Previous Message Kyotaro Horiguchi 2024-02-22 07:00:27 Re: BUG #18354: Aborted transaction aborted during cleanup when temp_file_limit exceeded