On Sun, 23 Jun 2024 19:14:09 +0900
Yugo NAGATA wrote:
> and Operator Families"? Additionally, is it useful to add LEAKPROOF
> information
> to the result of psql \dAo(+) meta-comand, or a function that can check given
> index
> or operator is leakproof or not?
I worte a pach to implement the p
On Sat, 18 May 2024 16:54:52 -0700
Josh Snyder wrote:
> When deploying RLS, I was surprised to find that certain queries which used
> only builtin indexes and operators had dramatically different query plans
> when
> a policy is applied. In my case, the query `tsvector @@ tsquery` over a GIN
>
When deploying RLS, I was surprised to find that certain queries which used
only builtin indexes and operators had dramatically different query plans when
a policy is applied. In my case, the query `tsvector @@ tsquery` over a GIN
index was no longer able to use that index. I was able to find one
