Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
>> Planner (find_usable_indexes function, actually) could push pathkey
>> expression into restriction clauses of index. I'm not fully satisfied
>> with this piece of code, but, may be, someone has a better idea. I
>> though about adding separate indexorderquals in IndexPath structure...
> Done, IndexScan and IndexPath have separate field to store order clauses.
Why? Isn't that redundant with the pathkey structures? We generate
enough paths during a complex planning problem that I'm not in favor
of adding unnecessary structures to them.
regards, tom lane