Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eJOtP-0005Ob-55 for pgsql-general@arkaria.postgresql.org; Mon, 27 Nov 2017 19:16:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eJOtO-0000DL-F9 for pgsql-general@arkaria.postgresql.org; Mon, 27 Nov 2017 19:16:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eJOtO-0000D5-7r for pgsql-general@lists.postgresql.org; Mon, 27 Nov 2017 19:16:34 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eJOtJ-0003Tp-Sm for pgsql-general@postgresql.org; Mon, 27 Nov 2017 19:16:33 +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 vARJGPUi014347; Mon, 27 Nov 2017 14:16:25 -0500 From: Tom Lane To: Thomas Munro cc: Jakub Glapa , Forums postgresql Subject: Re: ERROR: too many dynamic shared memory segments In-reply-to: References: Comments: In-reply-to Thomas Munro message dated "Tue, 28 Nov 2017 07:53:46 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14345.1511810185.1@sss.pgh.pa.us> Date: Mon, 27 Nov 2017 14:16:25 -0500 Message-ID: <14346.1511810185@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Thomas Munro writes: > Ah, so you have many Gather nodes under Append? That's one way to eat > arbitrarily many DSM slots. We allow for 64 + 2 * max_backends. Does > it help if you increase max_connections? I am concerned about the > crash failure mode you mentioned in the first email though: we should > always be able to handle that condition gracefully. I suspect this is an instance of the issue I complained about before [1] that parallel query is unable to cope with worker start failure. regards, tom lane [1] https://www.postgresql.org/message-id/4905.1492813727@sss.pgh.pa.us