Postgres Pro
Downloads
Home   >   mailing lists

Re: Windows service is not starting sothere’s message in log: FATAL: "could not create sharedmemory segment“Global/PostgreSQL.851401618”: Permissiondenied” - Mailing list pgsql-hackers

From Dmitry Vasilyev
Subject Re: Windows service is not starting sothere’s message in log: FATAL: "could not create sharedmemory segment“Global/PostgreSQL.851401618”: Permissiondenied”
Date
Msg-id 1444921511.3661.13.camel@postgrespro.ru
Whole thread Raw
In response to Windows service is not starting so there’smessage in log: FATAL: "could not create shared memory segment“Global/PostgreSQL.851401618”: Permissiondenied”  (Dmitry Vasilyev <d.vasilyev@postgrespro.ru>)
Responses Re: [HACKERS] Windows service is not starting so there’s message in log: FATAL: "could not create shared memory segment “Global/PostgreSQL.851401618”: Permission denied”  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
Tree view 
I think that function dsm_impl_windows() with EACCES error should not
do ereport() with FATAL level. It works, but it is likely to make an
infinite loop if the user will receive EACCES error.

On Чт, 2015-10-15 at 17:46 +0300, Dmitry Vasilyev wrote:
>  I’ve created 2 unprivileged users: user1 and user2; and registered 2
> services thorough pg_ctl register respectively under these 2 users.
> If
> first service is running second could not start and vice versa.
>
>
> ----
> Dmitry Vasilyev
> Postgres Professional: http://www.postgrespro.com
> Russian Postgres Company
>
>
>
--


----
Dmitry Vasilyev
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
Attachment

pgsql-hackers by date:

Previous
From: Dmitry Vasilyev
Date:
Subject: Windows service is not starting so there’smessage in log: FATAL: "could not create shared memory segment“Global/PostgreSQL.851401618”: Permissiondenied”
Next
From: Alvaro Herrera
Date:
Subject: Re: Fix unclear comments in tablecmds.c