Re: [PATCH] pg_hba.conf error messages for logical replication connections - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: [PATCH] pg_hba.conf error messages for logical replication connections
Date
Msg-id CAA4eK1J=5sNB9XspkjiZM9jpaio7nZRY7tdZa4=gC-_8g2Ba5A@mail.gmail.com
Whole thread Raw
In response to [PATCH] pg_hba.conf error messages for logical replication connections  (Paul Martinez <paulmtz@google.com>)
Responses Re: [PATCH] pg_hba.conf error messages for logical replication connections  (Paul Martinez <paulmtz@google.com>)
List pgsql-hackers
On Thu, Jan 28, 2021 at 1:51 PM Paul Martinez <paulmtz@google.com> wrote:
>
> Hey, all,
>
> When creating a logical replication connection that isn't allowed by the
> current pg_hba.conf, the error message states that a "replication
> connection" is not allowed.
>
> This error message is confusing because although the user is trying to
> create a replication connection and specified "replication=database" in
> the connection string, the special "replication" pg_hba.conf keyword
> does not apply.
>

Right.

> I believe the error message should just refer to a
> regular connection and specify the database the user is trying to
> connect to.
>

What exactly are you bothered about here? Is the database name not
present in the message your concern or the message uses 'replication'
but actually it doesn't relate to 'replication' specified in
pg_hba.conf your concern? I think with the current scheme one might
say that replication word in error message helps them to distinguish
logical replication connection error from a regular connection error.
I am not telling what you are proposing is wrong but just that the
current scheme of things might be helpful to some users. If you can
explain a bit how the current message mislead you and the proposed one
solves that confusion that would be better?

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: Assertion fail with window function and partitioned tables
Next
From: Neha Sharma
Date:
Subject: Re: [HACKERS] Custom compression methods