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: <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <zhouqq(at)cs(dot)toronto(dot)edu>,<icub3d(at)gmail(dot)com>,<pgsql-admin(at)postgresql(dot)org>
Subject: Re: ERROR: could not read block
Date: 2005-11-16 18:11:21
Message-ID: 437B21E90200002500000781@gwmta.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
Ran with this change.  Didn't take long to hit it.

Let me know if there's anything else I can do.

[2005-11-16 11:59:29.015 ] 4904 <dtr dtr 165.219.88.22(60649)> LOG: 
read failed on relation 1663/16385/1494810: -1 bytes, 1450
[2005-11-16 11:59:29.015 ] 4904 <dtr dtr 165.219.88.22(60649)> ERROR: 
could not read block 25447 of relation 1663/16385/1494810: Invalid
argument

>>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>  >>>

I think this is just cosmetic, but try %ld instead of %d in the elog
format strings.


Responses

pgsql-admin by date

Next:From: Qingqing ZhouDate: 2005-11-16 18:25:36
Subject: Re: ERROR: could not read block
Previous:From: Wim BertelsDate: 2005-11-16 17:53:28
Subject: Re: md5 collision generator

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