Re: Unclamped row estimates whith OR-ed subplans - Mailing list pgsql-performance

From Michael Lewis
Subject Re: Unclamped row estimates whith OR-ed subplans
Date
Msg-id CAHOFxGobHxN5euHRcEs2WPg3WsYev4WAd9xFAUwHwhyzUztfDw@mail.gmail.com
Whole thread Raw
In response to Re: Unclamped row estimates whith OR-ed subplans  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Unclamped row estimates whith OR-ed subplans
Next
From: Kenneth Marshall
Date:
Subject: PostgreSQL 12.3 slow index scan chosen