Skip site navigation (1) Skip section navigation (2)

Re: ERROR: could not read block

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Qingqing Zhou"<zhouqq(at)cs(dot)toronto(dot)edu>,<icub3d(at)gmail(dot)com>,<pgsql-admin(at)postgresql(dot)org>,"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Subject: Re: ERROR: could not read block
Date: 2005-11-15 16:29:38
Message-ID: 4379B89302000025000006E6@gwmta.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
Could my issue be the same problem as this thread?:

http://archives.postgresql.org/pgsql-bugs/2005-11/msg00114.php

The references to "Invalid Argument" caught my eye.  That thread
did start from a very different point, though.

-Kevin


>>> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>  >>>
It appears that the log file is not being written -- I'll start a
separate thread on that issue.

I reran the query.  Same error, same relation, different block.

dtr=> UPDATE
dtr->     "DbTranRepository"
dtr-> SET "userId" = UPPER("userId")
dtr-> WHERE (
dtr(>     ("userId" <> UPPER("userId")) AND
dtr(>     ("timestampValue" BETWEEN '2005-10-28' AND '2005-11-15'));
ERROR:  could not read block 1118215 of relation 1663/16385/16483:
Invalid argument

-Kevin


Responses

pgsql-admin by date

Next:From: Joshua MarshDate: 2005-11-15 16:42:27
Subject: Re: ERROR: could not read block
Previous:From: codeWarriorDate: 2005-11-15 16:01:03
Subject: Re: Timestamp not working

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group