Merge join doesn't seem to break early when I (and planner) think it should - 10.4

2019-12-26 Thread Timothy Garnett
Hi all, Query plan quick link: https://explain.depesz.com/s/JVxn Version: PostgreSQL 10.4 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609, 64-bit tbl: ~780 million rows, bigint primary key (keytbl), col1 is smallint and there is an index on (col1, col2) tmp

Is it possible to specify minimum number of rows planner should consider?

2020-09-28 Thread Timothy Garnett
Is there some way to tell the planner that unless it's guaranteed by a constraint or some such it shouldn't guess that the selectivity of a filter/anti-join is 1 row (e.g. minimum to consider is 2 rows unless it's guaranteed to be 1 row) or somehow otherwise make it more conservative around the wor

Re: Is it possible to specify minimum number of rows planner should consider?

2020-09-29 Thread Timothy Garnett
b/postgres/commit/b1fd99f4deffbbf3db2172ccaba51a34f18d1b1a > > On Mon, Sep 28, 2020 at 2:07 PM Tom Lane wrote: > >> Timothy Garnett writes: >> > Is there some way to tell the planner that unless it's guaranteed by a >> > constraint or some such it shouldn'