Re: [PATCH] Query Jumbling for CALL and SET utility statements

> Please find attached v2 as an attempt to do so.

+1 to the idea.

I think it will be better to evaluate jstate instead of

JUMBLE_UTILITY, such as:

if (query->utilityStmt && !jstate)

instead of

if (query->utilityStmt && !JUMBLE_UTILITY(query->utilityStmt))

This will allow for support of potentially other utility statements

In the future without having to teach pg_stat_statements about them.

If a jstate is set for the utility statements, pgss will do the right thing.

Thanks

--

Sami Imseih

Amazon Web Services (AWS)