| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: First-draft release notes for back branches are up |
| Date: | 2019-05-04 01:29:43 |
| Message-ID: | 10832.1556933383@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Sat, May 4, 2019 at 10:29 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> + Tolerate <literal>EINVAL</literal> and <literal>ENOSYS</literal>
> + error results, where appropriate, for fsync calls (Thomas Munro,
> + James Sewell)
> Nit-picking: ENOSYS is for sync_file_range, EINVAL is for fsync.
Yeah, I didn't really think it was worth distinguishing. If there
is some more general term that covers both calls, maybe we should
use that?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-05-04 01:36:24 | Re: improving wraparound behavior |
| Previous Message | Thomas Munro | 2019-05-04 01:07:01 | Re: First-draft release notes for back branches are up |