hivemind makes several global changes to database that are mildy questionable

Probably disables JIT, also likely forces planner to look at up to 16 joins. At some point we should reassess.

Same settings are applied to global Postgres configuration holding HAF database.

Well, that's good, as at least we don't have to do testing with and without hivemind for accurate performance testing :-) Still something to change eventually, in case we make global changes, then get surprised that hivemind when run secretly reverts them.

yes, probably there is one valid solution - move such settings to each function attributes.

Yep. I'm not too concerned about it at the moment, just created this issue so it wouldn't be forgotten.

changed milestone to %JulyHivemind