From: Tom Lane <tgl@sss.pgh.pa.us>
To: contact@yorhel.nl
Cc: pgsql-bugs@lists.postgresql.org, Tomas Vondra <tomas.vondra@enterprisedb.com>
Subject: Re: BUG #16846: "retrieved too many tuples in a bounded sort"
Date: Sun, 31 Jan 2021 11:16:08 -0500
Message-ID: <3086429.1612109768@sss.pgh.pa.us> (raw)
In-Reply-To: <16846-ae49f51ac379a4cb@postgresql.org>
References: <16846-ae49f51ac379a4cb@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> I have a query that fails as follows:
> SELECT id FROM releases WHERE minage = 18 AND released <= 20210131 AND id
> IN(SELECT id FROM releases_lang WHERE lang = 'ja') ORDER BY released DESC,
> id LIMIT 50;
> ERROR: XX000: retrieved too many tuples in a bounded sort
> LOCATION: tuplesort_gettuple_common, tuplesort.c:2103
> Sadly I've not been able to create a minimum working example, but I have
> been able to reproduce this on our public database dumps. I've made an
> excerpt of the database with only the two referenced tables:
> https://s.vndb.org/u/vndb-releases-test-20210131.sql.gz (~5.5MB compressed).
I confirm this is reproducible on HEAD with the referenced test data.
(Load it into a utf8-encoding database, ANALYZE, and boom.)
I presume that the incremental-sort patch is at fault, though I've
not tried to run it to ground since I have no idea how that works.
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, contact@yorhel.nl, tomas.vondra@enterprisedb.com
Subject: Re: BUG #16846: "retrieved too many tuples in a bounded sort"
In-Reply-To: <3086429.1612109768@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