From: Tom Lane <tgl@sss.pgh.pa.us>
To: tharakan@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17022: SQL causing engine crash
Date: Wed, 19 May 2021 10:50:35 -0400
Message-ID: <3430325.1621435835@sss.pgh.pa.us> (raw)
In-Reply-To: <17022-8e7e280c9b4baedb@postgresql.org>
References: <17022-8e7e280c9b4baedb@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> SQLSmith is constantly crashing v13.3 with SQL(s) that appear linked to a
> PostGIS (v3.0.3) bug - see Error Report below.
Yeah, I agree, it's a postgis bug.
> I decided to post this here (backtracking on an earlier thought), since #0 /
> #1 are postgres functions and I wasn't really sure if the arguments to these
> functions are sanitized. For e.g. whether pg_detoast_datum_slice() is
> expected to check input bounds (count=40 in this case).
The trace shows that gserialized_datum_get_gidx_p is passing a NULL
datum pointer to pg_detoast_datum_slice. Whether the slice length
is appropriate seems like an academic question.
(It does look like that code validates sliceoffset and slicelength
and does something appropriate if they're outside the bounds of
the datum's size. But you gotta have a datum.)
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, tharakan@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17022: SQL causing engine crash
In-Reply-To: <3430325.1621435835@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