| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: read() returns ERANGE in Mac OS X |
| Date: | 2012-05-21 16:27:17 |
| Message-ID: | CA+Tgmob848Rc0oG0BAc_BvS1J6HqZAx-mey+eCu4jURKV5B96w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 21, 2012 at 12:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> If we were sure that the kernel error was permanent, then this argument
> would be moot: the data is gone already. The scary thought here is that
> it might be a transient error, such as a not-always-repeatable kernel
> bug. In that case, zeroing the page would indeed lose data that had
> been recoverable before.
Yeah, and in fact I think that's probably not a terribly remote
scenario. Also, if you're running on dying hardware, you really do
NOT want to force the kernel to write a whole bunch of pages back to
the dying disk in the midst of trying to pg_dump it before it falls
over. You just want to read what you can of what's there now.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-05-21 16:27:19 | Re: Archiver not exiting upon crash |
| Previous Message | Tom Lane | 2012-05-21 16:23:28 | Re: read() returns ERANGE in Mac OS X |