Re: Regarding access to a user

From: Lew <noone(at)lwsc(dot)ehost-services(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Regarding access to a user
Date: 2008-08-22 23:39:46
Message-ID: G7adndSBlO7e0zLVnZ2dnUVZ_hKdnZ2d@comcast.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general pgsql-sql

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

<http://www.postgresql.org/docs/8.3/interactive/auth-pg-hba-conf.html>

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tena Sakai 2008-08-23 04:19:39 Re: restoring from dump
Previous Message Tena Sakai 2008-08-22 22:56:37 Re: restoring from dump

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2008-08-23 00:34:53 Re: Re: can't get UPDATE ... RETURNING ... INTO ... to compile successfully
Previous Message Ruben Gouveia 2008-08-22 21:30:46 Ranking?

Browse pgsql-sql by date

  From Date Subject
Next Message Steve Johnson 2008-08-23 00:59:27 What is wrong with this PostgreSQL UPDATE statement??
Previous Message Tom Lane 2008-08-22 22:41:30 Re: Why *no* ambig·uous complain in select part?