Jeff Janes <jeff.janes@gmail.com> writes:
> On Fri, Jul 20, 2018 at 2:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> However, that could only fix the OP's problem for these particular
>> functions, which are a small fraction of the ones we have that take
>> collatable types but don't really care about collation. I kinda feel
>> like we should have invented an "ignores collation" function property,
>> so that such functions could be identified --- that would not only let
>> postgres_fdw handle this honestly, but we could refrain from throwing
>> unmatched-collations errors for cases where it doesn't really matter.
> Would this automatically apply to operators as well, like hstore's ->
> operator, once the fetchval function was marked?
Sure, just like a function's volatility (for example) applies to operators
based on it. It'd require a bit of additional code to make that happen,
but I'd expect that to be included in any patch for this purpose.
regards, tom lane
