Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZnS5P-0004QO-79 for pgsql-hackers@arkaria.postgresql.org; Sat, 17 Oct 2015 14:03:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZnS5O-0007T8-Pn for pgsql-hackers@arkaria.postgresql.org; Sat, 17 Oct 2015 14:03:50 +0000 Received: from makus.postgresql.org ([174.143.35.229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZnS5O-0007T2-8E for pgsql-hackers@postgresql.org; Sat, 17 Oct 2015 14:03:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZnS5H-0004qn-NN for pgsql-hackers@postgresql.org; Sat, 17 Oct 2015 14:03:49 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t9HE3drJ031462; Sat, 17 Oct 2015 10:03:39 -0400 From: Tom Lane To: Amit Kapila cc: Robert Haas , Dmitry Vasilyev , pgsql-hackers Subject: Re: =?UTF-8?Q?Re=3A_=5BHACKERS=5D_Re=3A_=5BHACKERS=5D_Windows_service_is_not_s?= =?UTF-8?Q?tarting_so_there=E2=80=99s_message_in_log=3A_FATAL=3A_=22could_not_creat?= =?UTF-8?Q?e_shared_memory_segment_=E2=80=9CGlobal=2FPostgreSQL=2E851401618=E2=80=9D=3A_P?= =?UTF-8?Q?ermission_denied=E2=80=9D?= In-reply-to: References: <1444920387.3661.7.camel@postgrespro.ru> <1444921511.3661.13.camel@postgrespro.ru> Comments: In-reply-to Amit Kapila message dated "Sat, 17 Oct 2015 15:34:43 +0530" Date: Sat, 17 Oct 2015 10:03:39 -0400 Message-ID: <31461.1445090619@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Amit Kapila writes: > On Sat, Oct 17, 2015 at 12:07 AM, Robert Haas wrote: >> Maybe we need to be using PostmasterRandom() rather than random() for >> the control segment name. > +1. Though I think it is better to investigate the actual cause before > doing this. BackendRun() deliberately prevents that from working. And it also sets srandom() to a new value for each subprocess, so that AFAICS this idea would be a net negative. If you are seeing duplicate key values getting selected, the problem is elsewhere. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers