| From: | mikael(dot)wallen(at)spark-vision(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #14423: Fail to connect to DB |
| Date: | 2016-11-14 09:07:17 |
| Message-ID: | 20161114090717.8763.93494@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 14423
Logged by: Mikael Wallen
Email address: mikael(dot)wallen(at)spark-vision(dot)com
PostgreSQL version: 9.4.10
Operating system: Windows 10 (Version 1607 OS Build 14393.447)
Description:
After recent Windows updates we are getting connection errors and the logs
are full of the following errors:
2016-11-14 10:00:43 CET LOG: could not reserve shared memory region
(addr=00000000022C0000) for child 0000000000000FE0: error code 487
2016-11-14 10:00:43 CET LOG: could not fork autovacuum worker process: No
error
We are also seeing the same issue on Windows 7 x64 and with PostgreSQL
versions 9.4.8, 9.5.2 and 9.5.5.
Errors saying "could not fork new process for connection: No error" are also
occurring when using pgadminIII as well as psql. Everything worked well
before the recent Windows updates. Is this somehow related to changes in
ASLR (address space layout randomization) and if so, is there any
workaround?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rick Otten | 2016-11-14 14:18:42 | Re: BUG #14420: Parallel worker segfault |
| Previous Message | Jari Kopponen | 2016-11-14 07:32:36 | Re: BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log. |