Re: Patch for fail-back without fresh backup

Поиск
Список
Период
Сортировка
От Fujii Masao
Тема Re: Patch for fail-back without fresh backup
Дата
Msg-id CAHGQGwFACw4xyOJK+Y7Dxm3zP49wzgFqxsAL3k+HYV=0cvriXQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Patch for fail-back without fresh backup  (Samrat Revagade <revagade.samrat@gmail.com>)
Ответы Re: Patch for fail-back without fresh backup  (Sawada Masahiko <sawada.mshk@gmail.com>)
Список pgsql-hackers
On Tue, Sep 17, 2013 at 3:45 PM, Samrat Revagade
<revagade.samrat@gmail.com> wrote:
>
>> > syncrep.c: In function ‘SyncRepReleaseWaiters’:
>> > syncrep.c:421:6: warning: variable ‘numdataflush’ set but not used
>> > [-Wunused-but-set-variable]
>> >
>>
>> Sorry I forgot fix it.
>>
>> I have attached the patch which I modified.
>>
>
> Attached patch combines documentation patch and source-code patch.

I set up synchronous replication with synchronous_transfer = all, and then I ran
pgbench -i and executed CHECKPOINT in the master. After that, when I executed
CHECKPOINT in the standby, it got stuck infinitely. I guess this was cased by
synchronous_transfer feature.

How does synchronous_transfer work with cascade replication? If it's set to all
in the "sender-side" standby, it can resolve the data page inconsistency between
two standbys?

Regards,

--
Fujii Masao



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

Предыдущее
От: Rod Taylor
Дата:
Сообщение: Re: record identical operator
Следующее
От: Haribabu kommi
Дата:
Сообщение: Re: insert throw error when year field len > 4 for timestamptz datatype