| 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-26 22:58:02 |
| Message-ID: | CAOR=d=2hWeeYAN1a6tmSjvaux1Lsg+apzgAz=dTAS47Kwjf7SQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-01-26 23:02:51 | Re: Don't Thread On Me (PostgreSQL related) |
| Previous Message | Gauthier, Dave | 2012-01-26 22:55:29 | Re: Preventing access temporarily. |