From: | Glauco Torres <torres(dot)glauco(at)gmail(dot)com> |
---|---|
To: | Will McCormick <wmccormick(at)gmail(dot)com> |
Cc: | "Rossi, Maria" <maria(dot)rossi(at)jackson(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Logging on without prompt for password |
Date: | 2015-10-20 16:15:52 |
Message-ID: | CAMd+QOT0W8B5bNxMjQuGSJ1d52kVd=oW8vBkD_5jFy=HVS2gCg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
2015-10-20 14:00 GMT-02:00 Will McCormick <wmccormick(at)gmail(dot)com>:
> Have you tried PGPASSWORD env variable and unset it. I find it especially
> useful when scripting.
>
> On Tue, Oct 20, 2015 at 10:38 AM, Rossi, Maria <maria(dot)rossi(at)jackson(dot)com>
> wrote:
>
>> Hi,
>>
>>
>>
>>
>>
>> Is there a way of enabling a user to logon without being prompted for
>> password? I know there is the .pgpass file, but this file requires the
>> port# and my server has several postgres clusters with different port#.
>> So, am not sure if I can use the .pgpass file.
>>
>>
>>
>> And at the pg_hba.conf file, the id already has ‘trust’ method, but it
>> is still being prompted for password.
>>
>>
>>
>> This id will be used for automated scanning and needs to run pg_dumpall.
>>
>>
>>
>> Thanks.
>>
>>
>>
>
You tried?
.pgpass
#Server 1
127.0.0.1:5432:user:password
#Server 2
127.0.0.1:5433:user:password
#Server 3
127.0.0.1:8899:user:password
pg_hba.conf
# Socket e localhost
local all all trust
host all all 127.0.0.1/32 trust
#Or external
host all user 10.10.10.38/32 trust
Regards,
Glauco Torres
From | Date | Subject | |
---|---|---|---|
Next Message | Glauco Torres | 2015-10-20 16:17:53 | Re: Logging on without prompt for password |
Previous Message | Rossi, Maria | 2015-10-20 16:15:14 | Re: Logging on without prompt for password |