| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: read() returns ERANGE in Mac OS X |
| Date: | 2012-05-21 15:54:15 |
| Message-ID: | CA+Tgmoa74ieK=aEQ_x33cHrBj_2G7WfwAHzWiBciA2VSqSdibQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, May 20, 2012 at 2:12 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
>> Yeah, an enum would be nicer than an additional GUC. I kinda keep forgetting
>> that we have those. Though to bikeshed, the GUC should probably be just called
>> 'zero_pages' and take the values 'never', 'missing', 'unreadable' ;-)
>
> Sounds reasonable to me ..
It seems like it would be nicer to have a setting that somehow makes
the system disregard errors and soldier on rather than actively
destroying your data. Not that I have an exact design in mind, but
zero_damaged_pages is a really fast way to destroy your data.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-05-21 15:57:09 | Re: External Open Standards |
| Previous Message | Andrew Dunstan | 2012-05-21 15:47:14 | release note item |