| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Add isolationtester spec for old heapam.c bug |
| Date: | 2016-02-29 17:06:56 |
| Message-ID: | 14847.1456765616@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
I wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
>> Add isolationtester spec for old heapam.c bug
> Hmmm ....
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=spoonbill&dt=2016-02-27%2000%3A00%3A06
> This failure looks a lot like the timing-related problems I was chasing
> last week with deadlock-hard on the CLOBBER_CACHE_ALWAYS critters.
> spoonbill isn't CLOBBER_CACHE_ALWAYS, but it uses some weird malloc debug
> stuff that slows it down by similar orders of magnitude. You seem to need
> to think about how to make this test less timing-dependent.
The plot thickens:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=guaibasaurus&dt=2016-02-29%2016%3A17%3A01
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-02-29 17:44:06 | Re: pgsql: Add isolationtester spec for old heapam.c bug |
| Previous Message | Tom Lane | 2016-02-29 15:49:02 | pgsql: Remove useless unary plus. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Dolgov | 2016-02-29 17:19:00 | Re: [PATH] Jsonb, insert a new value into an array at arbitrary position |
| Previous Message | Pavel Stehule | 2016-02-29 16:53:15 | Re: proposal: PL/Pythonu - function ereport |