On 01/09/18 18:25, Jeremy Finzel wrote: > > Interesting. > > So you were running 9.6.9 before, it triggered the issue (and was not > able to recover). You took a filesystem snapshot, started a 9.6.10 on > the snapshot, and it recovered without hitting the issue? > > > I am resposting this to the list and not only to Tomas. Tomas, I can’t > promise just yet to delve into this because given the patch fixes the > issue it’s obviously much lower priority for our team. Are you hoping > for me to confirm the exact scenario in which the 9.6.10 patch fixes the > bug? > > Actually, there were more things changed than that so I'm not positive > it was the last patch: > > BEFORE: > Provider - 9.6.8-1.pgdg16.04+1, pglogical 2.1.1-1.xenial+1 > Subscriber - 9.6.9-2.pgdg16.04+1, 2.1.1-1.xenial+1 > > AFTER: > Provider - 9.6.10-1.pgdg16.04+1, pglogical 2.2.0-3.xenial+1 > Subscriber - 9.6.10-1.pgdg16.04+1, pglogical 2.2.0-3.xenial+1 >
I finally managed to reproduce this and it's indeed fixed in the 9.6.10 by the commit da10d6a. It was caused by the issue with subtransaction and SnapBuilder snapshots described there. -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
