|From:||Dmitry Vasilyev <d(dot)vasilyev(at)postgrespro(dot)ru>|
|To:||Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>|
|Subject:||Re: Windows service is not starting so there’s message in log: FATAL: "could not create shared memory segment “Global/PostgreSQL.851401618”: Permission denied”|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Пт, 2015-10-16 at 09:02 +0530, Amit Kapila wrote:
> On Thu, Oct 15, 2015 at 8:35 PM, Dmitry Vasilyev <d(dot)vasilyev(at)postgres
> pro.ru> wrote:
> > 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.
> Currently we are using error level as ERROR for creating dsm during
> postmaster startup which is not right and rather we should use error
> level as LOG. Can you please try with the attached patch and see
> if the issue is fixed for you.
> Another some what related point is currently we are using random()
> function to ensure a unique name for dsm and it seems to me that
> it is always going to generate same number on first invocation (at
> thats what happening on windows) due to which you are seeing the
> error. Another options could be to append current pid or data
> path as we are doing in win32_shmem.c. I think this could be an
> optimization which can be done in addition to the fix attached (we
> do this as a separate patch as well, if we agreed to do anything).
> With Regards,
> Amit Kapila.
> EnterpriseDB: http://www.enterprisedb.com
In that case your patch is working. There was LOG level message with Permission denied (from the operation point it’s not clear how to respond to message like this).
But as I understand if operating system can’t create shared memory we will try to distinguish that chunk up to infinity.
As I see it’s better to stop instance in this case.
So I guess it’s a good idea to remain all as it is now (FATAL level) but add PostmasterPid to name (as you suggest). There’s patch in attachments.
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
|Next Message||Albe Laurenz||2015-10-16 09:33:51||Re: Allow ssl_renegotiation_limit in PG 9.5|
|Previous Message||Amit Kapila||2015-10-16 09:20:04||Re: TODO list updates|