From: | Marco van Tol <nospam(at)tols(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Disabling or forwarding external connections |
Date: | 2003-12-10 18:13:25 |
Message-ID: | pan.2003.12.10.18.13.24.215411@tols.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 10 Dec 2003 11:50:25 -0500, Hisham Al-Shurafa wrote:
> Hello, I've searched the archives and docs for an answer to my question,
> but did not find anything, so I was hoping someone can answer this
> question or point me to a useful doc:
>
> Is there a way in PostGreSQL to temporarily disable any external
> connections (or just disable external writes) to a certain database,
> without having to restart the postmaster? Local connections to the
> database would still be allowed.
I am not sure, but a thought that crossed my mind is that you can have a
firewall on the database server firewall off all connections you don't
want for the moment. I figured it wouldn't hurt posting this, ignore it if
it's useless. ;-) (Make sure that there are no active connections when
enabling the firewall)
> Better yet, is there a way to transparently forward connections from
> clients to another database? For example, client connects to db A but
> the postmaster really connects him to db B?
That a firewall should be able to do as well, with new connections at
least. :)
> Thanks for your help!
Hope it is! :-)
--
Marco van Tol
From | Date | Subject | |
---|---|---|---|
Next Message | Joel Rodrigues | 2003-12-10 18:28:50 | Re: spelling errors in query terms |
Previous Message | Joe Conway | 2003-12-10 17:27:27 | Re: Strange permission problem regarding pg_settings |