| From: | Erik Jones <erik(at)myemma(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | W S <ws3reg(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Way to shutdown/freeze/stop an individual database without taking postmaster down? |
| Date: | 2008-04-10 19:28:52 |
| Message-ID: | 8CD90C96-6873-440B-9140-2D470F48CB01@myemma.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Apr 10, 2008, at 2:37 PM, Craig Ringer wrote:
> I haven't checked whether pg_hba.conf rules are reloaded, but `pg_ctl
> reload' can re-read some settings without a postmaster restart. So you
> might be able to disallow access in pg_hba then reload.
>
> I'd be curious to know if that works and if/how it affects existing
> connections - though I can always test it myself.
Yes, a pg_ctl reload will reload pg_hba.conf and, iirc, it does not
kill any existing connections as the values in that file are checked
at time of connection, not time of config load.
Erik Jones
DBA | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2008-04-10 19:37:29 | Re: Way to shutdown/freeze/stop an individual database without taking postmaster down? |
| Previous Message | Brent Wood | 2008-04-10 18:55:41 | PG 8.3 review in Linux Mag |