Yes, you need to set recovery_target_time in your recovery.conf while performing recovery (http://www.postgresql.org/docs/9.3/static/recovery-target-settings.html). That could be a tricky thing - depends on that exactly you need. All those transactions, which were not committed at given timestamp, will be rollbacked, so read url above carefully. On Tue, Mar 25, 2014 at 8:19 AM, gianfranco caca <limpcaca@xxxxxxxxx> wrote: > Hai ilya, > > Thanks for the respond. The database is estimated over 100gb and the > workload will be high. Can we use a pg_basebackup with pitr to restore based > on transaction time? > > Thanks > > > On Tuesday, 25 March 2014, 15:13, Ilya Kosmodemiansky > <ilya.kosmodemiansky@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > Hi gianfranco, > > > How exactly large is your database and how heavy is a workload on it? > Usually if you have more than ~200Gb, better to use pg_basebackup > because pg_dump will take too long time. And please take in mind, that > pg_dump makes dump, which is actually not the same thing as a backup. > > Best regards, > Ilya > > On Tue, Mar 25, 2014 at 5:45 AM, gianfranco caca <limpcaca@xxxxxxxxx> wrote: >> Hai, >> >> Can anyone tell me the difference and performance between pgdump and >> pg_basebackup if I want to backup a large database. >> >> Thanks > > > > > -- > Ilya Kosmodemiansky, > > PostgreSQL-Consulting.com > tel. +14084142500 > cell. +4915144336040 > ik@xxxxxxxxxxxxxxxxxxxxxxxxx > > > -- > Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > > > -- Ilya Kosmodemiansky, PostgreSQL-Consulting.com tel. +14084142500 cell. +4915144336040 ik@xxxxxxxxxxxxxxxxxxxxxxxxx -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
