On Fri, Aug 26, 2016 at 11:33 AM, Tsunakawa, Takayuki <tsunakawa.ta...@jp.fujitsu.com> wrote: > Our customer hit a problem of cascading replication, and we found the cause. > They are using the latest PostgreSQL 9.2.18. The bug seems to have been > fixed in 9.4 and higher during the big modification of xlog.c, but it's not > reflected in older releases. > > The attached patch is for 9.2.18. This just borrows the idea from 9.4 and > higher. > > But we haven't been able to reproduce the problem. Could you review the > patch and help to test it? I would very much appreciate it if you could > figure out how to reproduce the problem easily. > [...] > LOG: out-of-sequence timeline ID 140 (after 141) in log file 652, segment > 117, offset 0
9.3 has addressed that by allowing streaming standbys to perform timeline jumps via the replication protocol. Doesn't this problem enter in this area? -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
