Message-ID: <a757dc17-2339-446c-b59c-bd0d1efb3aca@enterprisedb.com>
Date: Wed, 3 Jul 2024 19:40:18 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Hash Right join and seq scan
To: James Pang <jamespang886@gmail.com>,
 pgsql-performance@lists.postgresql.org
References: 
 <CAHgTRffB3SYu2oYYZSWCcF7Vf0AUU_QH-EDA8GeUCbJ5yyZZ-g@mail.gmail.com>
 <CAHgTRffpgT-qB1Cb=VW8z1ucS6ksGLtMrveqS2PFwiY=uEATyw@mail.gmail.com>
 <CAHgTRfeW+Oaj2SQDxZ3ie4EfeFAjoo9MSc3huqD5A43XAG90Tg@mail.gmail.com>
Content-Language: en-US
From: Tomas Vondra <tomas.vondra@enterprisedb.com>
In-Reply-To: 
 <CAHgTRfeW+Oaj2SQDxZ3ie4EfeFAjoo9MSc3huqD5A43XAG90Tg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/a757dc17-2339-446c-b59c-bd0d1efb3aca%40enterprisedb.com>
Precedence: bulk

Hi James,

I think it'd be much easier to help you with investigating this issue if
you shared the actual queries, and the full EXPLAIN ANALYZE output both
with and without disabled hashjoin. Or even better, share a script that
reproduces the issue (creates tables, loads data, runs the queries).

BTW you suggested each partition has ~250k rows, but the explain plan
snippet you shared does not seem to be consistent with that - it only
shows 2500-5000 rows per partition. If you run ANALYZE on the table,
does that change the plan?

regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company