From: | "Dhaval Shah" <dhaval(dot)shah(dot)m(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Errors during recovery of a postgres. Need some help understanding them... |
Date: | 2007-04-10 15:50:59 |
Message-ID: | 565237760704100850g131752caiceab8e1880afa21f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I am still learning the ropes, I guess. I am not able to understand
the following:
> The attempt to back up to the
> last checkpoint isn't going to happen if you keep it from crashing at
> the REDO DONE point.
Does the above statement mean that I am crashing my primary server at
the REDO DONE point and if that is the case, how do I avoid crashing
at the REDO DONE? Or is this something to be done at the standby?
Regards
Dhaval
On 4/9/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Dhaval Shah" <dhaval(dot)shah(dot)m(at)gmail(dot)com> writes:
> > The question I have is, how far does it look behind in time?
>
> I think you only need to hang onto the immediately preceding file;
> it only backs up to the last applied WAL record, and that's certainly
> not going to span multiple segment files. The attempt to back up to the
> last checkpoint isn't going to happen if you keep it from crashing at
> the REDO DONE point.
>
> regards, tom lane
>
--
Dhaval Shah
From | Date | Subject | |
---|---|---|---|
Next Message | Jorge Godoy | 2007-04-10 16:48:08 | Re: programmatic way to fetch latest release for a given major.minor version |
Previous Message | tom | 2007-04-10 15:17:51 | Re: Debian upgrade and PGSQL pid file |