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

2007-09-19 Thread Stefan Kaltenbrunner

Tom Lane wrote:

Stefan Kaltenbrunner [EMAIL PROTECTED] writes:

Tom Lane wrote:

Stefan Kaltenbrunner [EMAIL PROTECTED] 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_mothdt=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

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
  choose an index scan if your joining column's datatypes do not
  match


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

2007-09-19 Thread Stefan Kaltenbrunner
Andrew Dunstan wrote:
 
 
 Tom Lane wrote:
 Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
  
 Tom Lane wrote:

 Stefan Kaltenbrunner [EMAIL PROTECTED] 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_mothdt=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?


   
 
 pgbfprod=# select sysname, stage, snapshot from build_status where log ~
 $$read only \d+ of \d+ bytes$$;
  sysname   |stage |  snapshot 
 ---+--+-
 zebra  | InstallCheck | 2007-09-11 10:25:03
 wildebeest | InstallCheck | 2007-09-11 22:00:11
 baiji  | InstallCheck | 2007-09-12 22:39:24
 luna_moth  | InstallCheck | 2007-09-19 13:10:01

hmm all of those seem to fail the foreign key checks in a very similiar
way and that are vastly different platforms (windows,solaris,openbsd and
linux).


Stefan

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


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

2007-09-19 Thread Andrew Dunstan



Tom Lane wrote:

Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
  

Tom Lane wrote:


Stefan Kaltenbrunner [EMAIL PROTECTED] 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_mothdt=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?


  


pgbfprod=# select sysname, stage, snapshot from build_status where log ~ 
$$read only \d+ of \d+ bytes$$;
 sysname   |stage |  snapshot  
---+--+-

zebra  | InstallCheck | 2007-09-11 10:25:03
wildebeest | InstallCheck | 2007-09-11 22:00:11
baiji  | InstallCheck | 2007-09-12 22:39:24
luna_moth  | InstallCheck | 2007-09-19 13:10:01
(4 rows)


cheers

andrew


---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly