| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | samcoffey <samcoffey82(at)gmail(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Re: Connection rejected: could not fork new process for connection: Unknown error |
| Date: | 2014-02-21 18:49:31 |
| Message-ID: | 5292.1393008571@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
samcoffey <samcoffey82(at)gmail(dot)com> writes:
> The following is appearing in postgresql-2014-02-21_090639.log (This is the
> only log file I can find):
> 2014-02-21 09:08:10 GMT LOG: could not reserve shared memory region
> (addr=0000000002300000) for child 00000000000004FC: error code 487
> 2014-02-21 09:08:10 GMT LOG: could not fork autovacuum worker process: A
> blocking operation was interrupted by a call to WSACancelBlockingCall.
> This is the PostgreSQL 9.3 (localhost:5432) server running on Windows.
Hm ... recent Windows? You may need to turn off ASLR, see for instance
http://www.postgresql.org/message-id/52EB4751.2060205@2ndquadrant.com
AFAIK the proposed code changes to handle this automatically haven't
been committed yet, much less made it into any released version of PG.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pandu Poluan | 2014-02-23 14:52:59 | One PostgreSQL server for multiple apps? |
| Previous Message | samcoffey | 2014-02-21 17:40:25 | Re: Connection rejected: could not fork new process for connection: Unknown error |