Re: Re: Connection rejected: could not fork new process for connection: Unknown error
| От | Tom Lane |
|---|---|
| Тема | Re: Re: Connection rejected: could not fork new process for connection: Unknown error |
| Дата | |
| Msg-id | 5292.1393008571@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Connection rejected: could not fork new process for connection: Unknown error (samcoffey <samcoffey82@gmail.com>) |
| Ответы |
Re: Connection rejected: could not fork new process for connection:
Unknown error
|
| Список | pgsql-novice |
samcoffey <samcoffey82@gmail.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
В списке pgsql-novice по дате отправления: