Take a look at the -x option - this solved an issue for me. Quoting from 9.1: "Includes the required transaction log files (WAL files) in the backup. This will include all transaction logs generated during the backup. If this option is specified, it is possible to start a postmaster directly in the extracted directory without the need to consult the log archive, thus making this a completely standalone backup." -tom On Mon, Oct 15, 2012 at 4:06 PM, Daniel Serodio (lists) <daniel.lists@xxxxxxxxxxxxx> wrote: > Magnus Hagander wrote: > > On Mon, Oct 15, 2012 at 10:15 PM, Daniel Serodio (lists) > <daniel.lists@xxxxxxxxxxxxx> wrote: > > I was reading the documentation for pg_basebackup and it states that > resulting backups "can be used both for point-in-time recovery and as the > starting point for a log shipping or streaming replication standby servers". > > Should pg_basebackup also be used for "regular" backups, or only for > PITR/streaming replication? > > It's for "regular backups", based off PITR. > > I'm sorry, I don't understand what you mean by "based off PITR". Do I need > PITR enabled in order to use pg_basebackup, or do you mean that I won't lose > the ability to use PITR after restoring from a backup created with > pg_basebackup, or do you mean something else? > > Regards, > Daniel Serodio -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
