Kevin, assuming you will have some time to confirm that it has been fixed in some version some time next week, I’ve compiled the test steps in http://pastebin.com/4Uqc2kPv <http://pastebin.com/4Uqc2kPv>
Thanks once again > On 17/06/2015, at 14:40, Filipe Pina <filipe.p...@impactzero.pt> wrote: > > Hi Kevin, > > I have installed: > PostgreSQL 9.3.7 on x86_64-unknown-linux-gnu, compiled by gcc (Ubuntu > 4.8.2-19ubuntu1) 4.8.2, 64-bit > > But as you mentioned it should have been fixed in later versions, I've > upgraded to 9.4: > PostgreSQL 9.4.4 on x86_64-unknown-linux-gnu, compiled by gcc (Ubuntu > 4.8.2-19ubuntu1) 4.8.2, 64-bit > > Though I still get the failures on 9.4.4.. > > On Qua, Jun 17, 2015 at 12:52 , Kevin Grittner <kgri...@ymail.com> wrote: >> Filipe Pina <filipe.p...@impactzero.pt> wrote: >> >> if drop the foreign key constraint on stuff_ext table there are >> no failures at all… >> >> It is my recollection that we were excluding the queries used to >> enforce referential integrity constraints from the conflict >> tracking, so I am surprised you are seeing this. What is the exact >> version you are using (as reported by the version() function)? >> >> I am at a conference this week, away from my normal development >> environment; but I will take a look next week. >> >> Kevin Grittner
