| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | mschuch(at)avaya(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #14050: "could not reserve shared memory region" in postgresql log |
| Date: | 2016-04-03 20:58:20 |
| Message-ID: | 20160403205820.GA1610541@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Mar 29, 2016 at 09:38:04AM +0000, mschuch(at)avaya(dot)com wrote:
> PostgreSQL version: 9.3.5
> Operating system: Windows 7
> 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.
We had not seen this on Windows 7. From where did you download the PostgreSQL
binaries, or with which tools did you build them? Which antivirus and/or
anti-malware software does this system use?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-04-03 21:41:53 | Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |
| Previous Message | Simon Riggs | 2016-04-03 20:32:28 | Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |