Message-ID: <4BB06A24.3030208@itech7.com>
Date: Mon, 29 Mar 2010 14:21:48 +0530
From: Nilesh Govindarajan <lists@itech7.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.1.8) Gecko/20100301 Shredder/3.0.3
MIME-Version: 1.0
To: Guillaume Lelarge <guillaume@lelarge.info>
CC: pgsql-admin@postgresql.org
Subject: Re: Socket & TCP connections
References: <4BAF8DA9.2010000@itech7.com> <4BB00A9C.2040007@itech7.com>
	<4BB054D6.3040806@lelarge.info>
In-Reply-To: <4BB054D6.3040806@lelarge.info>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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
मेरा भारत महान !
मम भारत: महत्तम भवतु !