The problem is that we already have an Npgsql-specific EF.Functions.JsonExists() which accepts a single key, and translates to `@>`. UPDATE: EF.Functions.JsonExists() was renamed to JsonPathExists() on the EF side.