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 <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1kZbML-00089C-9z
	for pgsql-bugs@arkaria.postgresql.org; Mon, 02 Nov 2020 15:03:01 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1kZbMK-0001dm-9X
	for pgsql-bugs@arkaria.postgresql.org; Mon, 02 Nov 2020 15:03:00 +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 <tgl@sss.pgh.pa.us>)
	id 1kZbMK-0001df-3X
	for pgsql-bugs@lists.postgresql.org; Mon, 02 Nov 2020 15:03:00 +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 <tgl@sss.pgh.pa.us>)
	id 1kZbMH-0004BK-Hy
	for pgsql-bugs@lists.postgresql.org; Mon, 02 Nov 2020 15:02:59 +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 0A2F2suv641070;
	Mon, 2 Nov 2020 10:02:54 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tom Vijlbrief <tvijlbrief@gmail.com>
cc: pgsql-bugs@lists.postgresql.org,
        Tomas Vondra <tomas.vondra@2ndquadrant.com>
Subject: Re: BUG #16694: Server hangs in 100% CPU loop when decompressing a
 specific TOAST Postgis linestring
In-reply-to: 
 <CAOQrpVdd82ADYRJNHbGAzmMrEyamjczz=yb4tQ1kLWr5FkNH6g@mail.gmail.com>
References: <16694-f107871e499ec114@postgresql.org>
 <543595.1604267856@sss.pgh.pa.us> <578150.1604274357@sss.pgh.pa.us>
 <CAOQrpVdd82ADYRJNHbGAzmMrEyamjczz=yb4tQ1kLWr5FkNH6g@mail.gmail.com>
Comments: In-reply-to Tom Vijlbrief <tvijlbrief@gmail.com>
	message dated "Mon, 02 Nov 2020 10:30:54 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <641068.1604329374.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 02 Nov 2020 10:02:54 -0500
Message-ID: <641069.1604329374@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Precedence: bulk

Tom Vijlbrief <tvijlbrief@gmail.com> writes:
> Op ma 2 nov. 2020 om 00:45 schreef Tom Lane <tgl@sss.pgh.pa.us>:
>> 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=3D233=
0f4d3a87ac43b6ecd31bfd698384888ed03cb

> Yes, this patch fixes the problem.

Great, thanks for testing!

			regards, tom lane