On Tue, Sep 17, 2013 at 3:45 PM, Samrat Revagade <revagade.sam...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
