Re: [COMMITTERS] pgsql: Add isolationtester spec for old heapam.c bug

2016-02-29 Thread Tom Lane
Alvaro Herrera writes: > Tom Lane wrote: >> guaibasaurus is not a particularly slow machine, and it's not using any >> special build flags AFAICT. So I'm not sure what to make of this case, >> except that it proves the timing problem can manifest on normal builds. >

Re: [COMMITTERS] pgsql: Add isolationtester spec for old heapam.c bug

2016-02-29 Thread Alvaro Herrera
Tom Lane wrote: > I wrote: > > Alvaro Herrera writes: > >> Add isolationtester spec for old heapam.c bug > > > Hmmm > > > http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=spoonbill=2016-02-27%2000%3A00%3A06 > > > This failure looks a lot like the

Re: [COMMITTERS] pgsql: Add isolationtester spec for old heapam.c bug

2016-02-29 Thread Tom Lane
I wrote: > Alvaro Herrera writes: >> Add isolationtester spec for old heapam.c bug > Hmmm > http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=spoonbill=2016-02-27%2000%3A00%3A06 > This failure looks a lot like the timing-related problems I was chasing > last

Re: [COMMITTERS] pgsql: Add isolationtester spec for old heapam.c bug

2016-02-26 Thread Tom Lane
Alvaro Herrera writes: > Add isolationtester spec for old heapam.c bug Hmmm http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=spoonbill=2016-02-27%2000%3A00%3A06 This failure looks a lot like the timing-related problems I was chasing last week with

[COMMITTERS] pgsql: Add isolationtester spec for old heapam.c bug

2016-02-26 Thread Alvaro Herrera
Add isolationtester spec for old heapam.c bug In 0e5680f4737a, I fixed a bug in heapam that caused spurious deadlocks when multiple updates concurrently attempted to modify the old version of an updated tuple whose new version was key-share locked. I proposed an isolationtester spec file that