| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | acamargo(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15111: c between x and x gives bad planning |
| Date: | 2018-03-14 21:53:37 |
| Message-ID: | 31902.1521064417@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> Scenario: A table with columns a,b,c. Btree index on a,c. Gist index on b,c.
> A query with a clause a = y and c between x and x uses the gist index b,c
> instead of a,c, with very worst execution time than when c between x and z,
> even with small deltas (x,z), when the btree (a,c) is used.
This has been improved for v11, cf
https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=7d08ce286
That won't be back-patched, though --- even if we were inclined to take
the risk of doing so, the catalog changes make it impractical.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-03-14 23:12:26 | BUG #15112: Unable to run pg_upgrade with earthdistance extension |
| Previous Message | PG Bug reporting form | 2018-03-14 20:31:11 | BUG #15111: c between x and x gives bad planning |