Security change to ransackable attribute leads to potentially huge overhead when using postgresql about ransack

[lucashungaro]

Would be interested in knowing how other people are solving this. I'm working on upgrading a Rails 6 app to Rails 7 and taking Ransack from 2.x to 4.x, so this will probably be an issue unless we explicitly list each model's columns, which I guess is the most correct solution.

[sk-]

We were also hit by this wen upgrading from activeadmin 2 to version 3. We saw quite a degradation in our system, experiencing very slow load times and had to revert the change.

Basically, to maintain compatibility with the precious question we followed the recommendation of defining a ransackable_attributes method in the base application record, which called authorizable_ransackable_attributes.

[sk-]

Maybe authorizable_ransackable_attributes need to be cached in the adapter, just like ransackable_attributes is.