From: | Nilesh Govindarajan <lists(at)itech7(dot)com> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Socket & TCP connections |
Date: | 2010-03-29 08:51:48 |
Message-ID: | 4BB06A24.3030208@itech7.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 03/29/2010 12:50 PM, Guillaume Lelarge wrote:
> Le 29/03/2010 04:04, Nilesh Govindarajan a écrit :
>> Hi, it seems to be working now. Can somebody explain to me how ? See
>> this pg_hba.conf -
>>
>> # "local" is for Unix domain socket connections only
>> local all root trust
>> local all all md5
>> # IPv4 local connections:
>> #host all root 127.0.0.1/32 trust
>> #host all root ::1/128 trust
>> host all all 127.0.0.1/32 md5
>> host all all ::1/128 md5
>>
>> Its the same code I think which I wrote previously. But now it asks
>> password when connected through TCP and doesn't when connected directly
>> as psql -d postgres
>>
>> PLZ EXPLAIN !! I'm in a big confusion :?
>>
>
> You probably forgot to reload the configuration after modifying it, and
> then someone reloaded it or restarted the server, and PostgreSQL was
> able to use the new configuration.
>
>
Yeah may be. But I remember issuing killall -HUP postmaster after every
change.
--
Nilesh Govindarajan
Site & Server Administrator
www.itech7.com
मेरा भारत महान !
मम भारत: महत्तम भवतु !
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Münstermann | 2010-03-29 09:31:34 | Migration of PGDATA |
Previous Message | Guillaume Lelarge | 2010-03-29 07:20:54 | Re: Socket & TCP connections |