Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm setting up my own postgres database to use with a heroku app (I don't wanna pay $200 a month just to have postgis, I don't need a huge database or anything, just postgis). I'm enabling remote access to my postgres database but it seems I have to do it on a per-ip basis with something like the following line in my pg_hba.conf file:

host all all md5

Now that's all fine and good, except I have no idea from what ip heroku will be trying to access my database. I was considering just changing the line to:

host all all md5

But that feels dangerous. So two part question:

  1. Is this really as dangerous as I feel it is?

  2. If it really is as dangerous as I feel it is, is there a different way to approach the problem?

share|improve this question

Make sure you change pg_hba to only allow SSL connections and you should be ok. You should also look into certificate based authentication. You may be interested in the new $50/month production database plan instead of the previous $200/mo entry point.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.