By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,178 Members | 971 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,178 IT Pros & Developers. It's quick & easy.

Disabling or forwarding external connections

P: n/a
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.

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?

Thanks for your help!
Hisham

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
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

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.