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

Re: [HACKERS] ERROR: could not read block

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Magnus Hagander <mha(at)sollentuna(dot)net>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, tgl(at)sss(dot)pgh(dot)pa(dot)us,zhouqq(at)cs(dot)toronto(dot)edu, icub3d(at)gmail(dot)com, pgsql-admin(at)postgresql(dot)org,pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] ERROR: could not read block
Date: 2005-11-21 23:05:57
Message-ID: 20051121230556.GP19279@pervasive.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-hackers
On Thu, Nov 17, 2005 at 07:56:21PM +0100, Magnus Hagander wrote:
> The way I read it, a delay should help. It's basically running out of
> kernel buffers, and we just delay, somebody else (another process, or an
> IRQ handler, or whatever) should get finished with their I/O, free up
> the buffer, and let us have it. Looking around a bit I see several
> references that you should retry on it, but nothing in the API docs.
> I do think it's probably a good idea to do a short delay before retrying
> - at least to yield the CPU for one slice. That would greatly increase
> the probability of someone else finishing their I/O...

If that makes it into code, ISTM it would be good if it also threw a
NOTICE so that users could see if this was happening; kinda like the
notice about log files being recycled frequently.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-11-21 23:12:50
Subject: Re: PostgreSQL 8.1.0 catalog corruption
Previous:From: Bob IppolitoDate: 2005-11-21 22:50:39
Subject: Re: PostgreSQL 8.1.0 catalog corruption

pgsql-admin by date

Next:From: Qingqing ZhouDate: 2005-11-21 23:24:39
Subject: Re: [ADMIN] ERROR: could not read block
Previous:From: Qingqing ZhouDate: 2005-11-21 21:07:43
Subject: Re: [ADMIN] ERROR: could not read block

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