You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
yes this is totally normal
both those extensions are used, but not as a datasource so they're not "sampled" 'like pg_stat_statements and others are.
ftr this page has been entirely redesigned in v5 as it was a bit misleading, and those are now in a new "support extension" category which doesn't have a "sampled" information.
I've expected something like this; the only question remaining is
pg_stat_monitor from Percona saves samples for request PARAMETERS. Under our (moderate) load, it hangs deadly. Do you have or are you planning or do you know any WORKING solution to store parameters together with queries?
are you talking about parameters for queries executed with the extended protocol?
there's no plan for that, it would probably require some additional extension. what we support is sampling of constants used in where / join predicates with pg_qualstats. this is definitely not the same but maybe it could be enough for your needs.
Hello
I'm trying powa and see that powa extension is "not sampled", as well as hypopg
is it ok? Extension pows created in base powa, hypopg in both powa and production base
The text was updated successfully, but these errors were encountered: