| From: | "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [ADMIN] ERROR: could not read block |
| Date: | 2005-11-21 21:07:43 |
| Message-ID: | dltcu7$728$1@news.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-11-21 23:05:57 | Re: [HACKERS] ERROR: could not read block |
| Previous Message | Michael D. Sofka | 2005-11-21 20:36:24 | Re: Server Hardware Configuration |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-11-21 21:14:48 | Re: PostgreSQL 8.1.0 catalog corruption |
| Previous Message | Alvaro Herrera | 2005-11-21 20:52:57 | Re: PostgreSQL 8.1.0 catalog corruption |