Fix range check for effective_io_concurrency
authorAlvaro Herrera <[email protected]>
Tue, 24 May 2016 18:55:34 +0000 (14:55 -0400)
committerAlvaro Herrera <[email protected]>
Tue, 24 May 2016 18:55:34 +0000 (14:55 -0400)
commit0c7cd45b6d702253c09427929bcceb6e7fe9029a
tree71458325e92299345c2c977087df24e6ffae91c6
parentc45fb43c8448c5b710d4ef9774497e1789e070e5
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
src/backend/storage/buffer/bufmgr.c