BUG #14050: "could not reserve shared memory region" in postgresql log - Mailing list pgsql-bugs

From mschuch@avaya.com
Subject BUG #14050: "could not reserve shared memory region" in postgresql log
Date
Msg-id 20160329093804.2920.69843@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #14050: "could not reserve shared memory region" in postgresql log
Re: BUG #14050: "could not reserve shared memory region" in postgresql log
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      14050
Logged by:          Mathias Schuch
Email address:      mschuch@avaya.com
PostgreSQL version: 9.3.5
Operating system:   Windows 7
Description:

I see the following entries in the log file on customer site:

2016-03-16 14:44:27 EST LOG:  database system is ready to accept
connections
2016-03-16 14:44:27 EST LOG:  autovacuum launcher started
2016-03-16 14:45:27 EST LOG:  could not reserve shared memory region
(addr=0000000001BB0000) for child 00000000000004CC: error code 487
2016-03-16 14:45:27 EST LOG:  could not fork autovacuum worker process: A
blocking operation was interrupted by a call to WSACancelBlockingCall.


2016-03-16 14:45:28 EST LOG:  could not reserve shared memory region
(addr=0000000001BB0000) for child 000000000000047C: error code 487
2016-03-16 14:45:28 EST LOG:  could not fork autovacuum worker process: A
blocking operation was interrupted by a call to WSACancelBlockingCall.

I read in the release notes that this issue should be solved with 9.3.4 but
with 9.3.5 it isn't.

pgsql-bugs by date:

Previous
From: daveg@sonic.net
Date:
Subject: BUG #14051: GIN index creation fails with large number of duplicate keys
Next
From: David Steele
Date:
Subject: Re: [HACKERS] BUG #13854: SSPI authentication failure: wrong realm name used