Hi Guys,
Thanks for your help. I have this working but don't completely
understand what I did.
1. Here is how the .pgpass file was originally written by pgadmin:
127.0.0.1:5432:*:postgres:Password
:5432:*:django_dev:Password
2. This is the amended version which allows pgadmin to automatically
connect to the server. All I have done is add line 3. All 3 lines seem
to be required to log on to the server.
127.0.0.1:5432:*:postgres:Password
:5432:*:django_dev:Password
localhost:5432:*:django_dev:Password
So questions:
What exactly is the difference between 127.0.0.1 and localhost?
When there is no IP stated as in the second line what does that do?
How come a localhost line wasn't created automatically by pgadmin?
Thanks,
Andy
On Tue, Nov 27, 2012 at 5:43 PM, Dave Page <dpage@pgadmin.org> wrote:
> On Tue, Nov 27, 2012 at 5:27 PM, Fernando Hevia <fhevia@gmail.com> wrote:
>>
>> On Mon, Nov 26, 2012 at 9:55 AM, Andrew Taylor <andydtaylor@gmail.com>
>> wrote:
>>> [also posted to Django users Google group]
>>>
>>> Hi all,
>>>
>>> Can I bypass the need for password entry in pgadmin3 by
>>> changing/locating/permissioning a .pgpass files instead of modifying
>>> pg_hba.conf to 'trust'? pg_hba.conf currently set at md5 for
>>> everything.
>>>
>>> 1. I can merrily connect to the postgres server on my local ubuntu
>>> machine as user postgres in bash by "su postgres" then "psql".
>>> 2. But if I want to be able to use pgadmin 3 GUI without entering a
>>> password I need to do this as my user, andyt and this doesn't work (I
>>> did chmod 600 this file to give rw access to one owner only). This
>>> feels like a permissioning issue but with that chmod 600 restriction
>>> on pgpass I'm not sure how to progress.
>>>
>>>
>>
>> pgAdmin should use ~/.pgpass in unixes. At least that is what the
>> documentation says.
>
> It does, and the equivalent pgpass file on Windows.
>
>> You can make a quick test: create a new server entry with user & password
>> saved. Then check your ~/.pgpass file to see if the new server shows up.
>>
>> Make sure to comply the pgpass format and permission requirements:
>> http://www.postgresql.org/docs/current/interactive/libpq-pgpass.html
>
> Or just login once from pgAdmin and click the "Save Password" option.
> That'll write the pgpass file for you.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
