Re: Unclamped row estimates whith OR-ed subplans

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Benjamin Coutu <ben(dot)coutu(at)zeyos(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Unclamped row estimates whith OR-ed subplans
Date: 2020-06-19 18:37:12
Message-ID: CAHOFxGobHxN5euHRcEs2WPg3WsYev4WAd9xFAUwHwhyzUztfDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>
> While you're waiting, you might think about recasting the query to
> avoid the OR. Perhaps you could do a UNION of two scans of the
> transactions table?
>

Minor note- use UNION ALL to avoid the dedupe work if you already know
those will be distinct sets, or having duplicates is fine.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Kenneth Marshall 2020-06-19 19:49:14 PostgreSQL 12.3 slow index scan chosen
Previous Message Tom Lane 2020-06-19 18:16:49 Re: Unclamped row estimates whith OR-ed subplans