pgsql: Improve error reporting for unsupported effective_io_concurrency

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Improve error reporting for unsupported effective_io_concurrency
Date: 2018-09-28 20:12:19
Message-ID: E1g5z7b-0007aS-E3@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Improve error reporting for unsupported effective_io_concurrency setting.

Give a specific error complaining about lack of posix_fadvise() when
someone tries to set effective_io_concurrency > 0 on platforms
without that.

This probably isn't worth extensive back-patching, but I (tgl) felt
cramming it into v11 was reasonable.

James Robinson

Discussion: https://postgr.es/m/153771876450.14994.560017943128223619@wrigleys.postgresql.org
Discussion: https://postgr.es/m/A3942987-5BC7-4F05-B54D-2A0EC2914B33@jlr-photo.com

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/a8fb03fceadb5fe9698ff0182ca76b0640348e70

Modified Files
--------------
src/backend/utils/misc/guc.c | 10 ++++++++--
src/include/pg_config_manual.h | 4 +++-
2 files changed, 11 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Stephen Frost 2018-09-28 23:05:50 pgsql: Add application_name to connection authorized msg
Previous Message Tom Lane 2018-09-28 19:49:13 pgsql: Tweak MSVC build system to match changes in 7143b3e82.