Re: Allowing extensions to supply operator-/function-specific info - Mailing list pgsql-hackers

From Paul Ramsey
Subject Re: Allowing extensions to supply operator-/function-specific info
Date
Msg-id B256FF5D-EF73-4FDE-A50D-9C9E9FB3B159@cleverelephant.ca
Whole thread Raw
In response to Re: Allowing extensions to supply operator-/function-specific info  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Allowing extensions to supply operator-/function-specific info
List pgsql-hackers

> On Mar 4, 2019, at 1:13 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Paul Ramsey <pramsey@cleverelephant.ca> writes:
>> I had what seemed to be working code except for a couple rare cases,
>> but when I fixed those cases it turned out that I had a major problem:
>> building a <var> OP <const> expression works fine, but building a
>> <const> OP <var> expression returns me an error.
>
> Yup, you're not supposed to do that.  The output expression *must* have
> the index key on the left, it's up to you to commute the operator if
> needed to make that happen.

Gotcha, done and now have an implementation that passes all our regression tests.

Thanks!

P

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Making all nbtree entries unique by having heap TIDs participatein comparisons
Next
From: Thomas Munro
Date:
Subject: Re: Rare SSL failures on eelpout