From: Tom Lane <tgl@sss.pgh.pa.us>
To: 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
Date: Sun, 01 Nov 2020 18:45:57 -0500
Message-ID: <578150.1604274357@sss.pgh.pa.us> (raw)
In-Reply-To: <543595.1604267856@sss.pgh.pa.us>
References: <16694-f107871e499ec114@postgresql.org>
<543595.1604267856@sss.pgh.pa.us>
> PG Bug reporting form <noreply@postgresql.org> writes:
>> This looks to me like a low level issue with Postgres13 and TOAST objects 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=postgresql.git;a=patch;h=2330f4d3a87ac43b6ecd31bfd698384888ed03...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, tvijlbrief@gmail.com, tomas.vondra@2ndquadrant.com
Subject: Re: BUG #16694: Server hangs in 100% CPU loop when decompressing a specific TOAST Postgis linestring
In-Reply-To: <578150.1604274357@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox