BUG #18414: When the key values are the same, the memory limit is exceeded when making a hash join

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: 723609220apple(at)gmail(dot)com
Subject: BUG #18414: When the key values are the same, the memory limit is exceeded when making a hash join
Date: 2024-03-28 12:51:15
Message-ID: 18414-6ace9250aab89519@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18414
Logged by: linfeng chen
Email address: 723609220apple(at)gmail(dot)com
PostgreSQL version: 16.2
Operating system: openeuler
Description:

/*
* Did this batch receive ALL of the tuples from its
* parent batch? That would indicate that further
* repartitioning isn't going to help (the hash values
* are probably all the same).
*/
create table t1(a int);
create table t2(a int);
insert into t1 values(1);
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t1 select * from t1;
insert into t2 select * from t1;
select count(*) from t1 join t2 on t1.a=t2.a;

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-03-28 16:16:23 BUG #18415: Logical replication errors.
Previous Message Andrey M. Borodin 2024-03-28 06:32:58 Re: BUG: deadlock between autovacuum worker and client backend during removal of orphan temp tables with sequences