pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: zhouqq@cs.toronto.edu
Cc: icub3d@gmail.com
Cc: pgsql-admin@postgresql.org
Subject: Re: ERROR: could not read block
Date: Tue, 15 Nov 2005 19:25:47 -0500
Message-ID: <29806.1132100747@sss.pgh.pa.us> (raw)
In-Reply-To: <4379DF3D0200002500000714@gwmta.wicourts.gov>
References: <4379DF3D0200002500000714@gwmta.wicourts.gov>

"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> ERROR:  could not read block 1482762 of relation 1663/16385/16483:
> Invalid argument

> So the block number is increasing each time.  I'm inclined to think
> that this is the result of the scan passing over rows added by itself.

It's just about impossible to believe that you would get an error at the
block I/O level due to a higher-level issue like "scan passing over rows
added by itself".

What I *could* believe, on the other hand, is that there's some problem
with reading blocks recently added to the file.  As I said before, we
really really need to find out what the Windows-level error code is
--- "Invalid argument" isn't telling us anything useful here.

			regards, tom lane



view thread (41+ messages)  latest in thread

Message-ID: <29806.1132100747@sss.pgh.pa.us>
Permalink:  ../29806.1132100747@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/29806.1132100747@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, Kevin.Grittner@wicourts.gov, zhouqq@cs.toronto.edu, icub3d@gmail.com
  Subject: Re: ERROR: could not read block
  In-Reply-To: <29806.1132100747@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox