I want to have a master-slave setup mainly for backups (but a hot read replica would be an added bonus). I have been using WAL replication earlier using Skytools walmgr utility. After upgrading to 9.1, I have explored streaming replication and it works nicely. However, here are some points which I need a confirmation about: 1. If we are using streaming replication, stopping and starting a slave server will always require a base backup from the primary. This is not the case with WAL replication if the WAL archives are being continuously shipped. (Base backups could be costly and slow if the involve hundreds of GB of data..) 2. In streaming replication, after the catchup phase, there are no WALs saved on the slave and therefore not available for replay. So, PITR will not be possible. Therefore, if what we need is a backup facility it's better to go with WAL replication (log shipping) instead of streaming replication because streaming replication is like RAID as Bruce Momjian says. Is that a correct conclusion? Or is it that I am missing something here? Is it an issue with walmgr3 rather than PostgreSQL? Thanks in advance. Regards, sayeed -- View this message in context: http://postgresql.1045698.n5.nabble.com/You-cannot-do-PITR-with-streaming-replication-true-tp5720050.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
