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

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.


-- 
Guillaume.
 http://www.postgresqlfr.org
 http://dalibo.com