Thank you Ian. I'm clear now.
--
View this message in context:
http://www.nabble.com/PITR-archive_timeout-Command-tp24788681p24790968.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to
Essentially, my question here is
1) What is the advantage / disadvantage of setting "archive_timeout" command
to too small or too high value?
2) What is the impact of setting this value during PITR recovery process?
--
View this message in context:
http://www.nabble.com/PITR-archive_timeout-Co
Hi Ian,
Ian Lea wrote:
>
> "We could stop the replay at any point and have a
> consistent snapshot of the database as it was at that time. Thus, this
> technique supports point-in-time recovery: it is possible to restore
> the database to its state at any time since your base backup was
> taken
base is reverted back:
1) Exactly the database was at 10:15 am
2) Exactly the database was at 10:00 am, because the last WAL archive
before 10:15 am was at 10:00 am.
Regards,
Gnanam
--
View this message in context:
http://www.nabble.com/PITR-archive_timeout-Command-tp24788681p2
