Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id A57CA64FD35 for ; Fri, 22 Aug 2008 21:05:35 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 61908-07 for ; Fri, 22 Aug 2008 21:05:07 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id 387EE64FCDF for ; Fri, 22 Aug 2008 21:05:12 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.14.1/8.14.1) with ESMTP id m7N04tXJ064987 for ; Fri, 22 Aug 2008 21:04:55 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.14.1/8.14.1/Submit) id m7MNdijU042828 for pgsql-admin@postgresql.org; Fri, 22 Aug 2008 20:39:44 -0300 (ADT) (envelope-from news) Date: Fri, 22 Aug 2008 19:39:46 -0400 From: Lew User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 X-Newsgroups: pgsql.admin Subject: Re: Regarding access to a user References: <48ABD192.EE98.0025.0@wicourts.gov> <48AD3037.6060700@batory.org.pl> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Message-ID: Lines: 24 X-Usenet-Provider: http://www.giganews.com X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.39 To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200808/148 X-Sequence-Number: 29993 Shashwat_Nigam wrote: > Dear Tomasz There are others here, too. > I had done the same but still the problem is like that the user is able to access all the databases in the current server. Even the order is like same and if I comment the second line(all access) then the error is there. > Please provide solution for the same. It sounds like you didn't bump the server. You have to signal it to re-read the pg_hba.conf file. The link provided by Kevin Grittner explains > The pg_hba.conf file is read on start-up and when the main server process > receives a SIGHUP signal. If you edit the file on an active system, you will > need to signal the server (using pg_ctl reload or kill -HUP) to make it > re-read the file. Did you perform that step? -- Lew