Re: [ADMIN] ERROR: could not read block - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: [ADMIN] ERROR: could not read block
Date
Msg-id 438DC09C02000025000009BA@gwmta.wicourts.gov
Whole thread Raw
List pgsql-hackers
[Apologies for the delayed response; fighting through a backlog.]

I checked with out DBAs, and they are willing to test it.

By they way, they found that they were getting this on a pg_dump,
too.  We will test both failure cases.  If the test goes OK, we would
be happy to leave it in production with this patch.

-Kevin


>>> "Qingqing Zhou" <zhouqq@cs.toronto.edu>  >>>

"Tom Lane" <tgl@sss.pgh.pa.us> wrote
>
> Would a simple retry loop actually help?  It's not clear to me how
> persistent such a failure would be.
>

[with reply to all followup threads] Yeah, this is the key and we
definitely 
have no 100% guarantee that several retries will solve the problem -
just as 
the situation in pg_unlink/pg_rename. But shall we do something now? If 
Kevin could help on testing(you may have to revert the registry changes
:-() 
, I would like to send a patch in the retry style.

Regards,
Qingqing 



---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster



pgsql-hackers by date:

Previous
From: Kenneth Marshall
Date:
Subject: Re: Shared locking in slru.c
Next
From: Andrew Dunstan
Date:
Subject: Re: [pgsql-www] Upcoming PG re-releases