From: | <furuyao(at)pm(dot)nttdata(dot)co(dot)jp> |
---|---|
To: | <masao(dot)fujii(at)gmail(dot)com> |
Cc: | <sawada(dot)mshk(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, <teranishih(at)nttdata(dot)co(dot)jp> |
Subject: | Re: pg_receivexlog --status-interval add fsync feedback |
Date: | 2014-08-21 05:54:17 |
Message-ID: | A9C510524E235E44AE909CD4027AE196BF7C70D19A@MBX-MSG-SV03.msg.nttdata.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> When replication slot is not specified in pg_receivexlog, the flush
> location in the feedback message always indicates invalid. So there seems
> to be no need to send the feedback as soon as fsync is issued, in that
> case.
> How should this option work when replication slot is not specified?
Thanks for the review!
The present is not checking the existence of specification of -S.
The use case when replication slot is not specified.
Because it does fsync, it isn't an original intention.
remote_write is set in synchronous_commit.
To call attention to the user, append following documents.
"If you want to report the flush position to the server, should use -S option."
Regards,
--
Furuya Osamu
Attachment | Content-Type | Size |
---|---|---|
pg_receivexlog-fsync-feedback-v4.patch | application/octet-stream | 9.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Haribabu Kommi | 2014-08-21 05:59:16 | Implementing parallel sequence doubts |
Previous Message | Michael Paquier | 2014-08-21 05:27:01 | Re: Support for N synchronous standby servers |