diff options
| author | Thomas Munro <tmunro@postgresql.org> | 2019-02-24 13:38:15 +1300 |
|---|---|---|
| committer | Thomas Munro <tmunro@postgresql.org> | 2019-02-24 22:44:18 +1300 |
| commit | 387483e89b2851247e091013bfdbfd1c448cb7df (patch) | |
| tree | 8ab8c74876af6f6154d1cb362de3dd50a8c5cdbf /src/backend/executor/nodeHash.c | |
| parent | 58947fbd56d1481a86a03087c81f728fdf0be866 (diff) | |
| download | postgresql-387483e89b2851247e091013bfdbfd1c448cb7df.tar.gz postgresql-387483e89b2851247e091013bfdbfd1c448cb7df.zip | |
Tolerate ENOSYS failure from sync_file_range().
One unintended consequence of commit 9ccdd7f6 was that Windows WSL
users started getting a panic whenever we tried to initiate data
flushing with sync_file_range(), because WSL does not implement that
system call. Previously, they got a stream of periodic warnings,
which was also undesirable but at least ignorable.
Prevent the panic by handling ENOSYS specially and skipping the panic
promotion with data_sync_elevel(). Also suppress future attempts
after the first such failure so that the pre-existing problem of
noisy warnings is improved.
Back-patch to 9.6 (older branches were not affected in this way by
9ccdd7f6).
Author: Thomas Munro and James Sewell
Tested-by: James Sewell
Reported-by: Bruce Klein
Discussion: https://postgr.es/m/CA+mCpegfOUph2U4ZADtQT16dfbkjjYNJL1bSTWErsazaFjQW9A@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeHash.c')
0 files changed, 0 insertions, 0 deletions