Re: curious regression failures (was Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded)

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: curious regression failures (was Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded)
Date: 2007-09-19 15:22:34
Message-ID: 46F13EBA.8000306@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> 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?

looks like it is in a similiar place:

http://www.kaltenbrunner.cc/files/regression.diffs (I don't have more
than this on that failure any more)

Stefan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-09-19 15:55:59 Re: curious regression failures (was Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded)
Previous Message Tom Lane 2007-09-19 15:14:20 curious regression failures (was Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded)

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2007-09-19 15:55:59 Re: curious regression failures (was Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded)
Previous Message Tom Lane 2007-09-19 15:14:20 curious regression failures (was Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded)