| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | curious regression failures (was Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded) |
| Date: | 2007-09-19 15:14:20 |
| Message-ID: | 20616.1190214860@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> Tom Lane wrote:
>> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>>> ! ERROR: could not read block 2 of relation 1663/16384/2606: read only 0 of 8192 bytes
>>
>> Is that repeatable? What sort of filesystem are you testing on?
>> (soft-mounted NFS by any chance?)
> doesn't seem to be repeatable :-(
Hmm ...
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=luna_moth&dt=2007-09-19%2013:10:01
Exact same error --- is it at the same place in the tests where you saw it?
Now that I think about it, there have been similar transient failures
("read only 0 of 8192 bytes") in the buildfarm before. It would be
helpful to collect a list of exactly which build reports contain
that string, but AFAIK there's no very easy way to do that; Andrew,
any suggestions?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2007-09-19 15:22:34 | Re: curious regression failures (was Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded) |
| Previous Message | Decibel! | 2007-09-19 15:01:12 | Re: Open issues for HOT patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2007-09-19 15:22:34 | Re: curious regression failures (was Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded) |
| Previous Message | Tom Lane | 2007-09-19 15:03:51 | Re: pg_next_dst_boundary optimization |