Re: Standalone synchronous master

Поиск
Список
Период
Сортировка
От Florian Pflug
Тема Re: Standalone synchronous master
Дата
Msg-id D8DE9B06-5D4C-4837-A79F-17A79BD0E472@phlo.org
обсуждение исходный текст
Ответ на Re: Standalone synchronous master  ("Joshua D. Drake" <jd@commandprompt.com>)
Ответы Re: Standalone synchronous master  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Standalone synchronous master  (Andres Freund <andres@2ndquadrant.com>)
Список pgsql-hackers
On Jan11, 2014, at 01:48 , Joshua D. Drake <jd@commandprompt.com> wrote:
> On 01/10/2014 04:38 PM, Stephen Frost wrote:
>> Adrian,
>> 
>> * Adrian Klaver (adrian.klaver@gmail.com) wrote:
>>> On 01/10/2014 04:25 PM, Stephen Frost wrote:
>>>> * Adrian Klaver (adrian.klaver@gmail.com) wrote:
>>>>> A) Change the existing sync mode to allow the master and standby
>>>>> fall out of sync should a standby fall over.
>>>> 
>>>> I'm not sure that anyone is argueing for this..
>>> 
>>> Looks like here, unless I am really missing the point:
>> 
>> Elsewhere in the thread, JD agreed that having it as an independent
>> option was fine.
> 
> Yes. I am fine with an independent option.

Hm, I was about to suggest that you can set statement_timeout before
doing COMMIT to limit the amount of time you want to wait for the
standby to respond. Interestingly, however, that doesn't seem to work,
which is weird, since AFAICS statement_timeout simply generates a
query cancel requester after the timeout has elapsed, and cancelling
the COMMIT with Ctrl-C in psql *does* work.

I'm quite probably missing something, but what?

best regards,
Florian Pflug




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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: [PATCH] pg_basebackup: progress report max once per second
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Standalone synchronous master