Re: PITR archive_timeout Command

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

--
Ian.

On Mon, Aug 3, 2009 at 11:50 AM, Gnanam<gnanam(at)zoniac(dot)com> wrote:
>
> 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:
>        9:00 am
>        9:30 am
>        10:00 am
>        10:30 am
>        11:00 am, etc.
>
> I specify PITR recovery time at 10:15 am in "recovery.conf".  My question
> is, to what time my database is recovered back?  At which stage of the
> following my database 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-tp24788681p24788681.html
> Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>