Re: could not fork autovacuum worker process: No error

On Sat, Apr 1, 2017 at 11:41 AM, Noah Misch <noah(at)leadboat(dot)com> wrote:
> On Wed, Jan 25, 2017 at 05:16:52PM +0100, Tomasz Szypowski wrote:
>> what do you suggest? Disabling ASLR? Do you know approx. how long will it
>> take for you to implement the change?

Last November I saw a high resurgence of such reports after a Windows
update. The builds in question had ASLR enabled and disabling it made
the trick but the update visibly made the failures more easier to show
up.

> We thought we implemented it years ago:
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=7f3e17b4827b61ad84e0774e3e43da4c57c4487f

I think that the OP here is asking for a solution where our shared
memory implementation is not messed up with ASLR enabled. And we don't
have a clear solution for that yet.

> On Wed, Jan 25, 2017 at 01:46:01PM +0100, Tomasz Szypowski wrote:
>> We use PostgreSQL 9.5.5 and 9.5.4. Both compiled from sources.
>
> Which compiler and compiler version did you use? What is the content of your
> config.pl or your ./configure command line?

Likely there are custom options used here, it may be good to look with
dumpbin what's the state of the builds.
--
Michael