From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Preventing access temporarily. |
Date: | 2012-01-27 00:27:04 |
Message-ID: | CAOR=d=1xTtu0sw3LYrvDdFAgNpEG5YcV-JHCzdpb6e_ZmtbwZw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jan 26, 2012 at 3:58 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Thu, Jan 26, 2012 at 3:55 PM, Gauthier, Dave <dave(dot)gauthier(at)intel(dot)com> wrote:
>> I found something else on the web.
>>
>> update pg_database set datallowconn = false where datname = 'foo';
>> update pg_database set datallowconn = true where datname = 'foo';
>>
>> Seems to have worked OK.
>>
>> Thanks for the pg_hab.conf suggestion. I'll add that to my notes.
>
> Yeah either of those will work. pg_hba.conf is nice for more complex
> setups and you can have several pg_hba.conf.whatever files laying
> about, link the right one and reload. So it's pretty easy to script
> and back out for complex stuff.
Oh and also you can revoke connect by user which allows for finer
grained control of connections as well.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-01-27 00:54:11 | Re: How to push predicate down |
Previous Message | Oliver Kohll | 2012-01-26 23:38:03 | Multi master use case? |