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 1kZN2y-0005ZW-5Z for pgsql-bugs@arkaria.postgresql.org; Sun, 01 Nov 2020 23:46:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kZN2x-0000xR-4J for pgsql-bugs@arkaria.postgresql.org; Sun, 01 Nov 2020 23:46:03 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kZN2w-0000xK-Uu for pgsql-bugs@lists.postgresql.org; Sun, 01 Nov 2020 23:46:02 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kZN2t-0003fs-En for pgsql-bugs@lists.postgresql.org; Sun, 01 Nov 2020 23:46:02 +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 0A1Njv6F578151; Sun, 1 Nov 2020 18:45:57 -0500 From: Tom Lane To: tvijlbrief@gmail.com cc: pgsql-bugs@lists.postgresql.org, Tomas Vondra Subject: Re: BUG #16694: Server hangs in 100% CPU loop when decompressing a specific TOAST Postgis linestring In-reply-to: <543595.1604267856@sss.pgh.pa.us> References: <16694-f107871e499ec114@postgresql.org> <543595.1604267856@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Sun, 01 Nov 2020 16:57:36 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <578149.1604274357.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 01 Nov 2020 18:45:57 -0500 Message-ID: <578150.1604274357@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > PG Bug reporting form writes: >> This looks to me like a low level issue with Postgres13 and TOAST objec= ts of >> a specific size and or compression behavior. = After looking at it some more, I'm pretty sure that these issues could explain your problem, though it's possible there's an additional contributing issue. If you're in a position to apply a patch and see whether it fixes the problem, please try https://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dpatch;h=3D2330f4= d3a87ac43b6ecd31bfd698384888ed03cb regards, tom lane