On Mon, Jul 28, 2014 at 9:38 PM, Alvaro Herrera
wrote:
> Robert Haas wrote:
>> OK, I think I see the problem. In EXEC_BACKEND mode,
>> SubPostmasterMain() calls InitProcess() before IsBackgroundWorker has
>> been set. InitProcess() therefore pulls the PGPROC for the worker
>> from freeProcs rath
Robert Haas wrote:
> OK, I think I see the problem. In EXEC_BACKEND mode,
> SubPostmasterMain() calls InitProcess() before IsBackgroundWorker has
> been set. InitProcess() therefore pulls the PGPROC for the worker
> from freeProcs rather than bgworkerFreeProcs. By exit time,
> IsBackgroundWorke
On Mon, Jul 28, 2014 at 3:59 PM, Robert Haas wrote:
> On Fri, Jul 25, 2014 at 3:25 PM, Noah Misch wrote:
>> On a Windows or other EXEC_BACKEND build, the following eventually gets
>> failures because all, or all but one, max_connections slot is consumed:
>>
>> for run in `seq 1 100`; do make -C
On Fri, Jul 25, 2014 at 3:25 PM, Noah Misch wrote:
> On a Windows or other EXEC_BACKEND build, the following eventually gets
> failures because all, or all but one, max_connections slot is consumed:
>
> for run in `seq 1 100`; do make -C contrib/test_shm_mq installcheck; done
>
> When I use max_
On a Windows or other EXEC_BACKEND build, the following eventually gets
failures because all, or all but one, max_connections slot is consumed:
for run in `seq 1 100`; do make -C contrib/test_shm_mq installcheck; done
When I use max_connections=40, it fails on the sixth iteration. Only the six
