BUG #14050: "could not reserve shared memory region" in postgresql log

From: mschuch(at)avaya(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #14050: "could not reserve shared memory region" in postgresql log
Date: 2016-03-29 09:38:04
Message-ID: 20160329093804.2920.69843@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: 14050
Logged by: Mathias Schuch
Email address: mschuch(at)avaya(dot)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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message daveg 2016-03-29 11:50:45 BUG #14051: GIN index creation fails with large number of duplicate keys
Previous Message Tom Lane 2016-03-28 23:27:51 Re: BUG #14049: Integer out of range on insert with default id