| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Greg Smith <greg(at)2ndquadrant(dot)com>, Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: fallocate / posix_fallocate for new WAL file creation (etc...) |
| Date: | 2013-05-30 13:51:28 |
| Message-ID: | CA+TgmobUDCVipdq6dck9TM2J0-bQ3LwHZ3TxCOQQc23OdDU+=Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 30, 2013 at 8:14 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> I don't think there's much danger of getting uninitialized data or
> such. That clearly would be insane. I think somebody might interpret it
> as read(2) returning an error until the page has been written to which
> isn't completely crazy.
In the absence of tangible evidence of some implementation that
behaves that way, I think that's just paranoia.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2013-05-30 14:05:24 | Re: pg_dump with postgis extension dumps rules separately |
| Previous Message | Robert Haas | 2013-05-30 13:47:22 | Re: removing PD_ALL_VISIBLE |