From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Recursively fsync() the data directory after a crash. |
Date: | 2015-05-18 16:04:23 |
Message-ID: | CA+TgmobjLyAGC_e6MHn_mNfBVibE7JKYQtE22AS8pLwfsMDoQA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Mon, May 18, 2015 at 11:04 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Sun, May 17, 2015 at 9:44 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>>> If there a reason why in pre_sync_fname(), the error message does not
>>> contain a %m?
>
>> For consistency with the rest of the file, I suppose. Not sure why
>> it's like that, but all the functions in the file do it that way.
>
> Huh? All the ones that are reporting kernel call failures certainly
> have %m.
Oops, you're right. I was looking at the wrong code. Yeah, that
should probably be fixed. I'm not sure it's a good idea to do that
right now though.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-05-18 16:09:31 | pgsql: Last-minute updates for release notes. |
Previous Message | Tom Lane | 2015-05-18 15:22:15 | Re: pgsql: hstore_plpython: Fix regression tests under Python 3 |