Re: PITR archive_timeout Command

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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."
> 

I got your point, again I've another simple question which I still don't
understand clearly.  Can I set my "archive_timeout" to 3600 seconds (1
hour), so that atleast I save my WAL archive storage space, because if it is
set to 1800 seconds (30 minutes), it is fast filling.  Setting it in this
way affect the PITR recovery process to consistent snapshot as the database
was at that time?  Will I be able to recover my database upto 10:15 am?

-- 
View this message in context: http://www.nabble.com/PITR-archive_timeout-Command-tp24788681p24789154.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux