| 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>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: write ahead logging in standby (streaming replication) |
| Date: | 2009-11-12 12:53:12 |
| Message-ID: | 1258030392.14054.189.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2009-11-12 at 21:45 +0900, Fujii Masao wrote:
> But, as I said on my first post on this thread, even such low-frequent
> fsync-WAL-before-buffer-flush might cause a response time spike on the
> primary because the walreceiver must sleep during that fsync. I think
> that leaving the WAL-logging business to another process like walwriter
> is a good idea for reducing further the impact on the walreceiver; In
> typical case,
Agree completely.
> Of course, since this approach is too complicated, it's out of the scope
> of the development for v8.5.
It's out of scope for phase 1, certainly.
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-11-12 13:13:56 | Re: New VACUUM FULL |
| Previous Message | Fujii Masao | 2009-11-12 12:45:35 | Re: write ahead logging in standby (streaming replication) |