Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kGjeh-0008Mv-D8 for pgsql-admin@arkaria.postgresql.org; Fri, 11 Sep 2020 14:03:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kGjeg-0000DX-AC for pgsql-admin@arkaria.postgresql.org; Fri, 11 Sep 2020 14:03:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kGjeg-0000DN-2n for pgsql-admin@lists.postgresql.org; Fri, 11 Sep 2020 14:03:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kGjed-0003en-Ip for pgsql-admin@postgresql.org; Fri, 11 Sep 2020 14:03:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 08BE3nEr370281; Fri, 11 Sep 2020 10:03:49 -0400 From: Tom Lane To: Jerry Sievers cc: pgsql-admin@postgresql.org Subject: Re: Pg11 server w/parallel backends unresponsive to cancel/terminate... (here are some backtraces) In-reply-to: <87blico2yh.fsf@jsievers.enova.com> References: <87imcko3zv.fsf@jsievers.enova.com> <87blico2yh.fsf@jsievers.enova.com> Comments: In-reply-to Jerry Sievers message dated "Fri, 11 Sep 2020 08:30:46 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <370279.1599833029.1@sss.pgh.pa.us> Date: Fri, 11 Sep 2020 10:03:49 -0400 Message-ID: <370280.1599833029@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Jerry Sievers writes: > Included a few backtraces... Hmm, seems like you've managed to hit an infinite loop in LLVM :-( That explains why it's not responding to SIGTERM - LLVM would not know that it's supposed to check for interrupts every so often. I'm afraid you'll have to go the immediate-shutdown route (and it'll still take a few seconds). Going forward, you should try to update to newest LLVM. Or disable JIT. regards, tom lane