Re: PITR archive_timeout Command - Mailing list pgsql-admin

From Ian Lea
Subject Re: PITR archive_timeout Command
Date
Msg-id 8c4e68610908030608r5799aa73k77704da74122471c@mail.gmail.com
Whole thread Raw
In response to Re: PITR archive_timeout Command  (Gnanam <gnanam@zoniac.com>)
Responses Re: PITR archive_timeout Command  (Gnanam <gnanam@zoniac.com>)
Re: PITR archive_timeout Command  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: PITR archive_timeout Command  (mattcwood <mattcwood@gmail.com>)
List pgsql-admin
> 1) What is the advantage / disadvantage of setting "archive_timeout" command
> to too small or too high value?

The advantage of setting it high is that you'll use less disk space
and have fewer files to archive.

The disadvantage of setting it high is that you might lose more data.

In your 30 minute example you could recover to 10:15 any time after
10:30, because a log file was archived at 10:30.  If archive_timeout
was set to 1 hour the log file wouldn't have been written till 11:00
and you would only have been able to roll forward to 10:00.

> 2) What is the impact of setting this value during PITR recovery process?

You mean whilst recovering the database?  I'm not aware of it having
any relevance during recovery.


--
Ian.

pgsql-admin by date:

Previous
From: Venkateswara Rao Bondada
Date:
Subject: Create table command fails with permission denied
Next
From: Gnanam
Date:
Subject: Re: PITR archive_timeout Command