| From: | Martin Pihlak <martin(dot)pihlak(at)gmail(dot)com> |
|---|---|
| To: | Sébastien Lardière <slardiere(at)hi-media(dot)com> |
| Cc: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, skytools-users(at)pgfoundry(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [Skytools-users] WAL Shipping + checkpoint |
| Date: | 2009-08-27 16:11:11 |
| Message-ID: | 4A96B01F.1020306@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>> There are actually no "real" data changes being made on your master
>> for some reason. So every time archive_timeout is reached a log full
>> of no changes is shipped to your slave and applied - and no checkpoint
>> times are changed for reasons I mentioned above.
>>
>>
>
> thanks, but we have not set archive_timeout, and we have a lot of real
> data changes.
>
> That's why i don't understand why checkpoint never happen on the slave.
>
What about the other values in pg_controldata output, do they change at
all? If they remain constant, maybe the logs are just not applied. Also,
are there any "restored log file xxx from archive" entries in postgres
log?
regards,
Martin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathaniel Smith | 2009-08-27 16:28:31 | Data audit trail techniques in postgresql |
| Previous Message | Joshua Tolley | 2009-08-27 14:29:54 | Re: Viable alternatives to SQL? |