On Tue, May 24, 2016 at 11:34 AM, Alvaro Herrera
wrote:
> Tom Lane wrote:
>> Jeff Janes writes:
>> > commit 1aba62ec made zero be an illegal value for effective_io_concurrency.
>> > i think this was an accident. If not, then the sample postgresql.conf
>> > (at least) needs to be updated.
>>
>> I
Tom Lane wrote:
> Jeff Janes writes:
> > commit 1aba62ec made zero be an illegal value for effective_io_concurrency.
> > i think this was an accident. If not, then the sample postgresql.conf
> > (at least) needs to be updated.
>
> It looks like the problem is that the new range check
>
> + /*
Jeff Janes writes:
> commit 1aba62ec made zero be an illegal value for effective_io_concurrency.
> i think this was an accident. If not, then the sample postgresql.conf
> (at least) needs to be updated.
It looks like the problem is that the new range check
+ /* This range check shouldn't fail
commit 1aba62ec made zero be an illegal value for effective_io_concurrency.
i think this was an accident. If not, then the sample postgresql.conf
(at least) needs to be updated.
Cheers,
Jeff
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscri