From: Qingqing Zhou <zhouqq@cs.toronto.edu>
To: pgsql-hackers@postgresql.org
Subject: Re: [ADMIN] ERROR: could not read block
Date: Thu, 17 Nov 2005 09:10:08 -0500
Message-ID: <dli2v6$if0$1@news.hub.org> (raw)
References: <6BCB9D8A16AC4241919521715F4D8BCE6C7BF4@algol.sollentuna.se>
""Magnus Hagander"" <mha@sollentuna.net> wrote
>
> Seems like we could just retry when we get this failure. The question is
> we need to do a small amount of sleep before we do? Also, we can't just
> retry forever, there has to be some kind of end to it...
> (If you read the SQL kb, it can be read as retrying is the correct
> thing, because the bug in sql was that it didn't retry)
>
Agree on the retry solution. Yes, two important factors are: intervals,
times. I suspect if it is a dedicated server, serveral retry can handle it.
But for a server might running backup together, who knows how long we need.
But in either way, I don't think an endless loop is needed -- at most 3
minutes (since s_lock() does this :-)).
Also, this is a partial solution to the "invalid parameter" win32 IO
problem. There are some other cases like ACESS_VIOLATION error need more
evidence to pin down.
Regards,
Qingqing
P.s. Go to be out of town for several days ...
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: zhouqq@cs.toronto.edu, pgsql-hackers@postgresql.org
Subject: Re: [ADMIN] ERROR: could not read block
In-Reply-To: <dli2v6$if0$1@news.hub.org>
* 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