pgsql: Fix range check for effective_io_concurrency - Mailing list pgsql-committers

From Alvaro Herrera
Subject pgsql: Fix range check for effective_io_concurrency
Date
Msg-id E1b5HWd-0001Ei-1g@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix range check for effective_io_concurrency

Commit 1aba62ec moved the range check of that option form guc.c into
bufmgr.c, but introduced a bug by changing a >= 0.0 to > 0.0, which made
the value 0 no longer accepted.  Put it back.

Reported by Jeff Janes, diagnosed by Tom Lane

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/0c7cd45b6d702253c09427929bcceb6e7fe9029a

Modified Files
--------------
src/backend/storage/buffer/bufmgr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [HACKERS] Re: pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <
Next
From: Tom Lane
Date:
Subject: pgsql: Avoid consuming an XID during vac_truncate_clog().