| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Mark Steben <msteben(at)autorevenue(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Warm Standby - log shipping |
| Date: | 2008-12-18 22:20:35 |
| Message-ID: | 1229638835.7559.15.camel@jd-laptop.pragmaticzealot.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, 2008-12-18 at 16:43 -0500, Mark Steben wrote:
> Hi folks,
> recovery mode, letting the updates catch up for the
> next days processing.
>
> My questions are:
>
> 1. Is this a proper usage of log shipping?
Sure but you will have to run a base backup every night. You can't exit
recovery, run queries, resume recovery. You have to exit recovery, run
queries, perform based backup, resume recovery.
> 3. I am currently in a state where a log got partially copied and postgres
> cannot find a valid checkpoint to restart. What is the best way to remedy
> this situation? Pg_resetxlog perhaps?
>
How did you do that? What are you using to copy the logs? You may want
to look at pitr tools. It will make your life easier:
https://projects.commandprompt.com/public/pitrtools
Joshua D. Drake
--
PostgreSQL
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Monnerie | 2008-12-18 23:18:20 | Re: DROP INDEX causes errors |
| Previous Message | Kevin Grittner | 2008-12-18 22:19:38 | Re: Warm Standby - log shipping |