Re: Removing unneeded self joins - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Removing unneeded self joins
Date
Msg-id CAM-w4HMS0N9y73AzwTwU_K9=25JMs0cTUoo_8MR_83Gh+Ci7wA@mail.gmail.com
Whole thread Raw
In response to Removing unneeded self joins  (Alexander Kuzmenkov <a.kuzmenkov@postgrespro.ru>)
List pgsql-hackers
I don't think the benchmarking that's needed is to check whether
pruning unnecessary joins is helpful. Obviously it's going to be hard
to measure on simple queries and small tables. But the resulting plan
is unambiguously superior and in more complex cases could extra i/o.

The benchmarking people were looking for in the past was testing the
impact of the extra planning work in cases where it doesn't end up
being applied. I'm not sure what the worst case is, perhaps a many-way
self-join where the join clauses are not suitable for pruning?



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Showing I/O timings spent reading/writing temp buffers in EXPLAIN
Next
From: Tom Lane
Date:
Subject: Re: Allow root ownership of client certificate key