Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

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

This is a feasibility/architectural question (I am no database administrator). Let's imagine a PostgreSQL database running online (like those from Heroku for example).

One would like to maintain a slave copy of this database on a remote PC by connecting to this online database (24/48 hour intervals). Is this possible from a PostgreSQL perspective? If yes, what would be the best Postgres implementation/configuration strategy? What do I need to learn?

The slave copy should catch up on all modifications made to the online database (eventually by specifying some kind of 'until' date if necessary). This slave would be used in read mode only. Ideally, slaves to the slave must be implemented in this asynchronous way too (i.e., in a cascading fashion).

share|improve this question

It's Postgres or PostgreSQL, not PostGre. The method you want is streaming replication or Point In Time Recovery (PITR) which is supported in 9.0 and above. It's covered in the docs. Read up on it, and then if you have any questions, come on back with them

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.