Re: Optimize mergejoinscansel() by avoiding redundant computations

From: ZizhuanLiu X-MAN <44973863(at)qq(dot)com>
To: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Optimize mergejoinscansel() by avoiding redundant computations
Date: 2026-10-22 10:57:13
Message-ID: tencent_4A54E30DBC62DB10EDF8C4CD3789E502F506@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,
Sorry, I forgot to include the initialization SQL.

drop table if exists pg_class_1;
drop table if exists pg_class_2;

select max(oid) from pg_catalog.pg_class;

create table pg_class_1 as select * from pg_catalog.pg_class where oid < 13673 WITH DATA;
create table pg_class_2 as select * from pg_class_1 WITH DATA;

analyze pg_class_1, pg_class_2;

select count(*) from pg_class_1;
select count(*) from pg_class_2;

explain (summary) select a.reltype from pg_class_1 a, pg_class_1 b where a.reltype = b.reltype;
explain (summary) select a.reltype from pg_class_1 a, pg_class_2 b where a.reltype = b.reltype;

regards,
--
ZizhuanLiu (X-MAN) 
44973863(at)qq(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vaijayanti Bharadwaj 2026-10-22 11:09:12 Fix concurrent-abort detection for subtransactions of prepared transactions
Previous Message ZizhuanLiu X-MAN 2026-10-22 10:42:49 Optimize mergejoinscansel() by avoiding redundant computations