From: | Jayadevan M <Jayadevan(dot)Maymala(at)ibsplc(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
Subject: | PostgreSQL PITR - more doubts |
Date: | 2010-07-12 11:23:19 |
Message-ID: | OFC2981E2C.FBD7D986-ON6525775E.003DEF04-6525775E.003E99D3@ibsplc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
Hello all,
One doubt about how PostgreSQL PITR works. Let us say I have all the
archived WALs for the past week with
archive_command = 'cp -i %p /home/postgres/archive/%f </dev/null'
I took a base backup last night. If I try to recover the server today
after
copying the base backup from yesterday and providing
restore_command = 'cp /home/postgres/archive/%f %p'
does PostgreSQL go through all the past week's archived WALS or
it can figure out that the base backup is from yesterday, so skip
a large number of archived WALs and start only from file xxx ?
Either way, are there ways to speed up the restore process?
Regards,
Jayadevan
DISCLAIMER:
"The information in this e-mail and any attachment is intended only for
the person to whom it is addressed and may contain confidential and/or
privileged material. If you have received this e-mail in error, kindly
contact the sender and destroy all copies of the original communication.
IBS makes no warranty, express or implied, nor guarantees the accuracy,
adequacy or completeness of the information contained in this email or any
attachment and is not liable for any errors, defects, omissions, viruses
or for resultant loss or damage, if any, direct or indirect."
From | Date | Subject | |
---|---|---|---|
Next Message | Jesper Krogh | 2010-07-12 11:38:29 | Re: PostgreSQL PITR - more doubts |
Previous Message | Fujii Masao | 2010-07-12 10:05:34 | Re: Queries about PostgreSQL PITR |
From | Date | Subject | |
---|---|---|---|
Next Message | Jesper Krogh | 2010-07-12 11:38:29 | Re: PostgreSQL PITR - more doubts |
Previous Message | A. Kretschmer | 2010-07-12 11:15:00 | Re: now() gives same time within the session |