| 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>, furuyao(at)pm(dot)nttdata(dot)co(dot)jp, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, teranishih(at)nttdata(dot)co(dot)jp |
| Subject: | Re: pg_receivexlog --status-interval add fsync feedback |
| Date: | 2014-10-23 15:01:47 |
| Message-ID: | CA+U5nMLv6Oen25qkNCje4+++=UMaL79nbw1UMCuA9gFBGApeRg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 23 October 2014 15:39, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> Sorry, I'm going around in the circle. But I'd like to say again, I don't think
> this is good idea. It prevents asynchronous pg_receivexlog from fsyncing
> WAL data and sending feedbacks more frequently at all. They are useful,
> for example, when we want to monitor the write location of asynchronous
> pg_receivexlog in almost realtime. But if we adopt the idea, since feedback
> cannot be sent soon in async mode, pg_stat_replication always returns
> the not-up-to-date location.
Why not send a message every 10 seconds when its not sync rep?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-10-23 15:11:58 | Re: pg_receivexlog --status-interval add fsync feedback |
| Previous Message | Michael Paquier | 2014-10-23 14:48:01 | Re: Simplify calls of pg_class_aclcheck when multiple modes are used |