Ian Lea wrote:
>
> 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.
>
This is not *entirely* true. The archive_timeout setting only indicates the
time at which a ne
Ian Lea wrote:
> The advantage of setting it high is that you'll use less disk space
> and have fewer files to archive.
Although you can mitigate the space problem by using pg_clearxlogtail
(combined with gzip) or pglesslog from pgfoundry.
-Kevin
--
Sent via pgsql-admin mailing list (pgsq
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
> 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 m
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
1) Exactly the database was at 10:15 am
From http://www.postgresql.org/docs/8.3/static/continuous-archiving.html
"There is nothing that says we have to replay the WAL entries all the
way to the end. We could stop the replay at any point and have a
consistent snapshot of the database as it was at
Hi,
I have a basic and quick question related to "archive_timeout" command in
PITR.
I've set "archive_timeout" to 1800 seconds (30 minutes) in
"postgresql.conf", which means WAL archives are generated every 30 minutes.
So, if for an example my WAL archives are generated at the following time:
