Abraham:
On Thu, 10 Apr 2025 at 13:30, Francisco Olarte wrote:
> You forgot to answer the first and most important question.
> > How are you connecting? Your symptoms matches confusing local with
> > TCP/IP to localhost. They are not the same thing.
After reading more messages it seems you use
On Wed, 9 Apr 2025 at 19:44, Abraham, Danny wrote:
> Thanks for the answers.
> All the 3 lines are, of course, uncommented for the test.
That was assumed.
> I am using Linux, socket is in /tmp, i see the .s files , but local trust
> still does not connect.
You forgot to answer the first and most
bject:* Re: [EXTERNAL] Re: Cannot connect local with ttrust
(pg_upgrade assumes it)
On Wed, Apr 9, 2025, 12:21 Abraham, Danny <mailto:danny_abra...@bmc.com>> wrote:
Thanks again.
Here is the example:
>>>>>>>>
dba-tlv-x6y64k% cat pg_hba.conf
#
sql (17.4)
Type "help" for help.
postgres=# \q
==>
-Original Message-
From: Adrian Klaver
Sent: Thursday, April 10, 2025 12:00 AM
To: Abraham, Danny ; David G. Johnston
; Francisco Olarte ;
pgsql-general@lists.postgresql.org
Subject: Re: [EXTERNAL] Re: Cannot connect l
On 4/9/25 13:40, Abraham, Danny wrote:
Thanks again.
4. I am not aware of an env variable that changes the top down matching
on pg_hba.conf
Should have added to previous post:
From here:
https://www.postgresql.org/docs/current/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT
a
10:34 PM
To: Abraham, Danny
Cc: Adrian Klaver ; Francisco Olarte
; pgsql-general@lists.postgresql.org
Subject: Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade
assumes it)
On Wed, Apr 9, 2025, 12:21 Abraham, Danny
mailto:danny_abra...@bmc.com>> wrote:
Thanks again.
Here
On Wed, Apr 9, 2025, 12:21 Abraham, Danny wrote:
> Thanks again.
> Here is the example:
>
> dba-tlv-x6y64k% cat pg_hba.conf
> # TYPE DATABASEUSERCIDR-ADDRESS METHOD
> local all all trust
> hostall all 0.0.0
On 4/9/25 12:23, Abraham, Danny wrote:
Thanks again.
Here is the example:
dba-tlv-x6y64k% cat pg_hba.conf
# TYPE DATABASEUSERCIDR-ADDRESS METHOD
local all all trust
hostall all 0.0.0.0/0 scram-s
nt: Wednesday, April 9, 2025 8:49 PM
To: Abraham, Danny ; Francisco Olarte
Cc: pgsql-general@lists.postgresql.org
Subject: Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade
assumes it)
On 4/9/25 10:45 AM, Abraham, Danny wrote:
> Failure eans going down the hba list and asking
nt: Wednesday, April 9, 2025 8:49 PM
To: Abraham, Danny ; Francisco Olarte
Cc: pgsql-general@lists.postgresql.org
Subject: Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade
assumes it)
On 4/9/25 10:45 AM, Abraham, Danny wrote:
> Failure eans going down the hba list and asking
On 4/9/25 10:45 AM, Abraham, Danny wrote:
Failure eans going down the hba list and asking for the password.
In pg_hba.conf first match wins, sounds like you have password auth line
before the trust lines.
You need to provide the complete pg_hba.conf auth lines you are working
with.
On 4/9/25 09:20, Abraham, Danny wrote:
Hi,
Asking for help with inability to connect local using trust
The # are comments that would 'hide' the lines below from being looked
at for authentication purposes.
Is this really how the lines are in your pg_hba.conf file?
Fail
#local all
On Wed, 9 Apr 2025 at 18:20, Abraham, Danny wrote:
> Asking for help with inability to connect local using trust
> Fail
> #local all all trust
> #local all dbauser peer
> OK
> #hostall all 127.0.0.1/32 trust
How are you c
On 4/9/25 10:44 AM, Abraham, Danny wrote:
Thanks for the answers.
All the 3 lines are, of course, uncommented for the test.
Then provide the actual configuration you are working with.
I am using Linux, socket is in /tmp, i see the .s files , but local
trust still does not connect.
Provid
Failure eans going down the hba list and asking for the password.
Sent from Workspace ONE Boxer
On Apr 9, 2025 20:04, Francisco Olarte wrote:
On Wed, 9 Apr 2025 at 18:20, Abraham, Danny wrote:
> Asking for help with inability to connect local using trust
> Fail
> #local all all
Thanks for the answers.
All the 3 lines are, of course, uncommented for the test.
I am using Linux, socket is in /tmp, i see the .s files , but local trust still
does not connect.
Sent from Workspace ONE Boxer
On Apr 9, 2025 20:04, Francisco Olarte wrote:
On Wed, 9 Apr 2025 at 18:20, Abraham, D
On Wed, Apr 9, 2025 at 9:20 AM Abraham, Danny wrote:
> Fail
>
Failures include messages indicating why. You should always share such
messages. Showing the command that produced the failure is also advised.
David J.
17 matches
Mail list logo
