remove nasty warnings

[pashagolub]

Now database log is full of

WARNING: only support const scalar array in qual: {SCALARARRAYOPEXPR :opno 98 :opfuncid 67 :hashfuncid 0 :negfuncid 0 :useOr true :inputcollid 100 :args ({OPEXPR :opno 3477 :opfuncid 3214 :opresulttype 25 :opretset false :opcollid 100 :inputcollid 100 :args ({COERCEVIAIO :arg {VAR :varno 2 :varattno 2 :vartype 25 :vartypmod -1 :varcollid 100 :varnullingrels (b) :varlevelsup 0 :varnosyn 2 :varattnosyn 2 :location -1} :resulttype 3802 :resultcollid 0 :coerceformat 1 :location -1} {CONST :consttype 25 :consttypmod -1 :constcollid 100 :constlen -1 :constbyval false :constisnull false :location -1 :constvalue 24 [ 96 0 0 0 103 97 116 104 101 114 95 119 97 110 116 101 100 95 115 116 97 116 117 115 ]}) :location -1} {CONST :consttype 1009 :consttypmod -1 :constcollid 100 :constlen -1 :constbyval false :constisnull false :location -1 :constvalue 60 [ -16 0 0 0 1 0 0 0 0 0 0 0 25 0 0 0 3 0 0 0 1 0 0 0 40 0 0 0 97 99 116 105 118 101 0 0 44 0 0 0 115 116 111 112 112 101 100 0 44 0 0 0 100 101 108 101 116 101 100 0 ]}) :location -1}]

This is extremely frustrating. I believe suck kind of messages are good for DEBUG level but not for INFO.

[if-loop69420]

Hi,

this is not something etcd_fdw does, but rather something that either supabase_wrappers, or pgrx itself does. I can't really change that i think

[if-loop69420]

https://github.com/supabase/wrappers/blob/main/supabase-wrappers/src/qual.rs#L320 it's this line in supabase_wrappers.

[pashagolub]

Damn! Should we fork it? :)

[pashagolub]

ok, another idea. It's just a WARNING level message. So can we set log level to ERROR during the start, so we don't receive all these?

[if-loop69420]

we can try that. either that or we fork

[if-loop69420]

This log level can be changed in postgres itself, not in pgrx. Maybe you can set the loglevel for the extension in the database?