| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Harris <lists(at)spuddy(dot)org> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Shutting down a warm standby database in |
| Date: | 2006-11-30 21:36:54 |
| Message-ID: | 747.1164922614@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Stephen Harris <lists(at)spuddy(dot)org> writes:
> On Thu, Nov 30, 2006 at 03:59:15PM -0500, Tom Lane wrote:
>> Actually I was misremembering that: the frequency of recovery
>> checkpoints is time-based, and for a slave that's in sync with its
>> master, they should occur about as often as checkpoints on the master.
>> So the amount of log to be replayed should be comparable to what the
>> master would have to replay if it crashed.
> As a test, I started a recover, recovered 11 archive logs
> (000000010000000000000035 to 00000001000000000000003F), some may have had
> activity; I not sure. I then waited 10 minutes after the last log file
> had been replayed. Then I did a fast shutdown. Starting the standby
> database again required it going back to 000000010000000000000035 again.
That case is not what I described --- you weren't tracking a live master
that's generating checkpoints.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-11-30 21:39:59 | Re: Shutting down a warm standby database in 8.2beta3 |
| Previous Message | rbaisak | 2006-11-30 21:34:58 | JDBC traffic logger |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-11-30 21:39:59 | Re: Shutting down a warm standby database in 8.2beta3 |
| Previous Message | Stephen Harris | 2006-11-30 21:31:51 | Re: Shutting down a warm standby database in |