| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL |
| Date: | 2010-03-19 08:52:04 |
| Message-ID: | 1268988724.3556.3.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-docs pgsql-hackers |
On Thu, 2010-03-18 at 23:27 +0900, Fujii Masao wrote:
> I agree that this is a bigger problem. Since the standby always starts
> walreceiver before replaying any WAL files in pg_xlog, walreceiver tries
> to receive the WAL files following the REDO starting point even if they
> have already been in pg_xlog. IOW, the same WAL files might be shipped
> from the primary to the standby many times. This behavior is unsmart,
> and should be addressed.
We might also have written half a file many times. The files in pg_xlog
are suspect whereas the files in the archive are not. If we have both we
should prefer the archive.
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-03-19 10:41:22 | pgsql: Reset btpo.xact following recovery of btree delete page. |
| Previous Message | Peter Eisentraut | 2010-03-18 20:00:51 | pgsql: Also print the libpq error message when lo_create or lo_open |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-03-19 11:37:08 | Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL |
| Previous Message | Tim Landscheidt | 2010-03-18 15:52:31 | [PATCH] Explain generate_subscripts() more clearly |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Csaba Nagy | 2010-03-19 08:59:23 | Re: Getting to beta1 |
| Previous Message | KaiGai Kohei | 2010-03-19 07:22:45 | [BUG] SECURITY DEFINER on call handler makes daemon crash |