Posted Nov 10, 2005 1:53 UTC (Thu) by yem (guest, #1138)
[Link]
It's there - just poorly documented. For example, to ensure you're taking a full backup you need to copy the CURRENT WAL log file. But the docs do not specify a way to tell which file that might be out of the dozen files in pg_xlog/. A reference backup and restore script would be great to have.
Still, the PITR system requires you to backup and restore the whole server in one go - you cannot do just one database (AFAIK). Slony1 appears to be able to handle database by database, but again the log shipping feature is underdocumented and geared towards replication. Slony is also fairly invasive in that it adds columns to your tables where required and requires all tables to be specified in slonik config/commands.