Chinmay Kanchi <cgkanchi(at)gmail(dot)com> writes:
> When checking equality with an operand that has additional nodes
> ("2".double()), GIN only considers the first node ("2"). So $.a ==
> "2".integer() looks up a match for the json string "2" instead of the
> number 2, and silently drops rows that a sequential scan would have
> returned.
Hmph, another bug in the same function as your previous report :-(.
Here's a less-WIP patch for both.
regards, tom lane