Re: could not fork autovacuum worker process: No error

Tom,

what do you suggest? Disabling ASLR? Do you know approx. how long will it
take for you to implement the change?

regards
Thomas

2017-01-25 17:04 GMT+01:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> Tomasz Szypowski <tomasz(dot)szypowski(at)gmail(dot)com> writes:
> > I send you logs
>
> Hmm ....
>
> 2016-11-10 17:58:42 CET LOG: could not reserve shared memory region
> (addr=015E0000) for child 0000085C: error code 487
> 2016-11-10 17:58:42 CET LOG: could not fork autovacuum worker process: No
> error
> 2016-11-10 17:58:43 CET LOG: could not reserve shared memory region
> (addr=015E0000) for child 00000828: error code 487
> 2016-11-10 17:58:43 CET LOG: could not fork autovacuum worker process: No
> error
> 2016-11-10 17:58:44 CET LOG: could not reserve shared memory region
> (addr=015E0000) for child 0000085C: error code 487
> 2016-11-10 17:58:44 CET LOG: could not fork autovacuum worker process: No
> error
> 2016-11-10 17:59:02 CET LOG: could not reserve shared memory region
> (addr=015E0000) for child 00000878: error code 487
> 2016-11-10 17:59:02 CET LOG: could not fork autovacuum worker process: No
> error
> 2016-11-10 17:59:03 CET LOG: could not reserve shared memory region
> (addr=015E0000) for child 00000874: error code 487
> 2016-11-10 17:59:03 CET LOG: could not fork autovacuum worker process: No
> error
> 2016-11-10 17:59:04 CET LOG: could not reserve shared memory region
> (addr=015E0000) for child 00000878: error code 487
> 2016-11-10 17:59:04 CET LOG: could not fork autovacuum worker process: No
> error
>
> Yeah, that probably is an ASLR problem :-(. We don't have a good
> solution for that on Windows yet.
>
> regards, tom lane
>