Re: could not fork autovacuum worker process: No error

From: Tomasz Szypowski <tomasz(dot)szypowski(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: could not fork autovacuum worker process: No error
Date: 2017-01-25 15:50:12
Message-ID: CACmJi2J-prqVinUGYBS+LX=ar1sw3+iAeJRhDCJ=rZUWRc+4Bw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

is a greate honour for me to meet you personally.
Thanks for the quick response as well.
Here is the log for autovaccum, but it doesn`t work with normal login as
well:
2016-11-16 08:57:03 CET LOG: could not reserve shared memory region
(addr=015E0000) for child 000012D4: error code 487
2016-11-16 08:57:03 CET LOG: could not fork autovacuum worker process: No
error

regards
Thomas

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

> Tomasz Szypowski <tomasz(dot)szypowski(at)gmail(dot)com> writes:
> > Hi PostgreSQL Team,
> > since last month we receive error as in the topic. After restart one can
> > work with server but not for long.
>
> > Is it connected with one of Windows Update on Server 2012 (or Windows 10)
> > ASLR?
>
> If this is on Windows, there's probably more information about the
> failure in the postmaster log --- look for LOG messages just before
> the "fork failure" complaint.
>
> regards, tom lane
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-01-25 16:04:56 Re: could not fork autovacuum worker process: No error
Previous Message Tomasz Szypowski 2017-01-25 15:46:15 Re: could not fork autovacuum worker process: No error