BUG #15618: Duplicating a join clause breaks index use

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: cdalxndr(at)yahoo(dot)com
Subject: BUG #15618: Duplicating a join clause breaks index use
Date: 2019-02-01 17:38:39
Message-ID: 15618-5357e448d7cbeb27@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 15618
Logged by: cd a
Email address: cdalxndr(at)yahoo(dot)com
PostgreSQL version: 10.3
Operating system: Windows 10
Description:

Adding a unused join clause to the query, modifies the run time from 50ms to
4seconds.
No columns from the join clause are returned and the joined table is not
used in other places.
The join clause is a duplicate of another one that is used for further
joining.

The joined clause should have been automatically removed as it has no side
effects, thus using indices and optimizing query runtime.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Stehule 2019-02-01 18:25:06 Re: BUG #15618: Duplicating a join clause breaks index use
Previous Message Petr Fedorov 2019-02-01 14:32:43 'update returning *' returns 0 columns instead of empty row with 2 columns when (i) no rows updated and (ii) when applied to a partitioned table with sub-partition