summaryrefslogtreecommitdiff
path: root/src/backend
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2016-05-24 14:55:34 -0400
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2016-05-24 14:55:34 -0400
commit0c7cd45b6d702253c09427929bcceb6e7fe9029a (patch)
tree71458325e92299345c2c977087df24e6ffae91c6 /src/backend
parentc45fb43c8448c5b710d4ef9774497e1789e070e5 (diff)
downloadpostgresql-0c7cd45b6d702253c09427929bcceb6e7fe9029a.tar.gz
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
Diffstat (limited to 'src/backend')
-rw-r--r--src/backend/storage/buffer/bufmgr.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/storage/buffer/bufmgr.c b/src/backend/storage/buffer/bufmgr.c
index c0d5fa74e1..e5dafaf00c 100644
--- a/src/backend/storage/buffer/bufmgr.c
+++ b/src/backend/storage/buffer/bufmgr.c
@@ -514,7 +514,7 @@ ComputeIoConcurrency(int io_concurrency, double *target)
*target = new_prefetch_pages;
/* This range check shouldn't fail, but let's be paranoid */
- return (new_prefetch_pages > 0.0 && new_prefetch_pages < (double) INT_MAX);
+ return (new_prefetch_pages >= 0.0 && new_prefetch_pages < (double) INT_MAX);
}
/*