Re: Patch for fail-back without fresh backup

Поиск
Список
Период
Сортировка
От Pavan Deolasee
Тема Re: Patch for fail-back without fresh backup
Дата
Msg-id CABOikdM7x=p0ymKNrVV6P+9Z77UpzkraV7F_4GSu2CDXQHUW+w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Patch for fail-back without fresh backup  (Sawada Masahiko <sawada.mshk@gmail.com>)
Ответы Re: Patch for fail-back without fresh backup  (Sawada Masahiko <sawada.mshk@gmail.com>)
Список pgsql-hackers



On Mon, Jun 24, 2013 at 7:17 PM, Sawada Masahiko <sawada.mshk@gmail.com> wrote:


--------------------
[Server]
standby_name = 'slave1'
synchronous_transfer = commit
wal_sender_timeout = 30
[Server]
standby_name = 'slave2'
synchronous_transfer = all
wal_sender_timeout = 50
-------------------

What different values/modes you are thinking for synchronous_transfer ? IMHO only "commit" and "all" may not be enough. As I suggested upthread, we may need an additional mode, say "data", which will ensure synchronous WAL transfer before making any file system changes. We need this separate mode because the failback safe (or whatever we call it) standby need not wait on the commits and it's important to avoid that wait since it comes in a direct path of client transactions.

If we are doing it, I wonder if an additional mode "none" also makes sense so that users can also control asynchronous standbys via the same mechanism.

Thanks,
Pavan

--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee

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

Предыдущее
От: Steve Singer
Дата:
Сообщение: Re: [PATCH] Fix conversion for Decimal arguments in plpython functions
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [9.4 CF 1] The Commitfest Slacker List