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
This commit is contained in:
Alvaro Herrera 2016-05-24 14:55:34 -04:00
parent c45fb43c84
commit 0c7cd45b6d

View File

@ -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);
}
/*