Bill Moran wrote:
- No reliability. On slow days, WAL logs could take a long time to
rotate, so small but important transactions might not be replicated
for a long time.
So it is all right for backup but for replication it could end up laking
too much behind, and a fail over could be hours behind.
So PITR can be used, but one of the cons is the unpredictable delay of
data. I thought one of the ideas behind the PITR system was to get
rather reason backups of data ...
/BL
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
