Opened 8 years ago
Closed 7 years ago
#3778 closed defect (invalid)
Weird COMMUTATOR and NEGATOR for btree operators
| Reported by: | strk | Owned by: | pramsey |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.5.0 |
| Component: | postgis | Version: | 2.3.x |
| Keywords: | Cc: |
Description
In the recent code review done for #3777 I noticed that all btree operators have a wrong COMMUTATOR or NEGATOR. I'm ticketting it rather than fixing right away because operators are one of those things non-easy to upgrade…
Also, I dubt the planner would ever use those as long as both operators have the same COST, so won't be easy to test either (and makes this ticket a moot point too…)
Change History (4)
comment:1 by , 8 years ago
| Milestone: | PostGIS 2.3.3 → PostGIS 2.4.0 |
|---|
comment:2 by , 7 years ago
| Milestone: | PostGIS 2.4.0 → PostGIS 2.5.0 |
|---|
comment:3 by , 7 years ago
Could you describe more what you see wrong with the COMMUTATOR and NEGATORs? I'm not seeing it.
comment:4 by , 7 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Thanks for looking at this, indeed I don't see any problem either.
Maybe it's just earlier in the day 
Closing as invalid.
Note:
See TracTickets
for help on using tickets.
pushing to 2.4 since might require a drop recreate. Too risky for 2.3