eaming =
on" doesn't help.
Regards,
[1]
https://www.postgresql.org/message-id/CAMnUB3oYugXCBLSkih%2BqNsWQPciEwos6g_AMbnz_peNoxfHwyw%40mail.gmail.com
[2]
https://www.postgresql.org/message-id/17974-f8c9d353a62f414d%40postgresql.org
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
ndividual objects within it) I also understand that it would
be better to avoid the risk of moving/removing superuser checks in
v13. So far the reported issues are only about making bloom trusted,
which seems not a common use case (right?). So probably we can come
back to this issue and discuss how to fix
on as possible.
>
I pushed the fix for this issue[1].
Regards,
[1]
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=d87d07b7ad3b782cb74566cd771ecdb2823adf6a
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com