| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: fast promotion and log_checkpoints |
| Date: | 2013-05-21 15:02:51 |
| Message-ID: | CA+U5nMKm6-9Tvy9zw9pJ9R4uXwAaF-SqNt5Xbq1Y=vA970nn+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 21 May 2013 15:29, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> Or, what about using CHECKPOINT_FORCE and just printing "force"?
> Currently that checkpoint always starts because of existence of the
> end-of-recovery record, but I think we should ensure that the checkpoint
> always starts by using that flag.
This would mean we can't use the secondary checkpoint record, but we
already gave that up so should be OK.
Three people, three suggestions; so I will agree to this suggestion so
we can get on with it.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benedikt Grundmann | 2013-05-21 15:59:26 | Re: streaming replication, "frozen snapshot backup on it" and missing relfile (postgres 9.2.3 on xfs + LVM) |
| Previous Message | Fujii Masao | 2013-05-21 14:29:15 | Re: fast promotion and log_checkpoints |