Re: pg_receivexlog --status-interval add fsync feedback

Поиск
Список
Период
Сортировка
От Fujii Masao
Тема Re: pg_receivexlog --status-interval add fsync feedback
Дата
Msg-id CAHGQGwGQ9EQp6hX5tVgVo6ko0hTZnYzwV4F1Rr4yC89Pqdqk3w@mail.gmail.com
обсуждение исходный текст
Ответ на pg_receivexlog --status-interval add fsync feedback  (<furuyao@pm.nttdata.co.jp>)
Ответы Re: pg_receivexlog --status-interval add fsync feedback  (<furuyao@pm.nttdata.co.jp>)
Список pgsql-hackers
On Tue, Aug 12, 2014 at 6:19 PM,  <furuyao@pm.nttdata.co.jp> wrote:
> Hi all,
>
> This patch is to add setting to send status packets after fsync to --status-interval of pg_receivexlog.
>
> If -1 is specified to --status-interval, status packets is sent as soon as after fsync.

I don't think that it's good idea to control that behavior by using
--status-interval. I'm sure that there are some users who both want
that behavior and want set the maximum interval between a feedback
is sent back to the server because these settings are available in
walreceiver. But your version of --status-interval doesn't allow those
settings at all. That is, if set to -1, the maximum interval between
each feedback cannot be set. OTOH, if set to the positive number,
feedback-as-soon-as-fsync behavior cannot be enabled. Therefore,
I'm thinking that it's better to introduce new separate option for that
behavior.

Regards,

-- 
Fujii Masao



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Haribabu Kommi
Дата:
Сообщение: Re: [BUGS] BUG #9652: inet types don't support min/max
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: Inconsistent use of --slot/-S in pg_receivexlog and pg_recvlogical