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
Which is incomplete because AFAICT Nginx can't remove a header based on a value OOTB. It will always remove the whole header. We'd need OpenResty for this.
Now, this problem has already been solved with the estimated and planned count.
We just need to disable the Prefer: count=exact. We can do this with a config option.
db-exact-count-enable = false
The text was updated successfully, but these errors were encountered:
steve-chavez
added
enhancement
a feature, ready for implementation
config
related to the configuration options
idea
Needs of discussion to become an enhancement, not ready for implementation
and removed
enhancement
a feature, ready for implementation
labels
May 8, 2023
We currently rely on this guide for protecting against full counts on big tables: https://postgrest.org/en/v10.2/admin.html#count-header-dos
Which is incomplete because AFAICT Nginx can't remove a header based on a value OOTB. It will always remove the whole header. We'd need OpenResty for this.
Now, this problem has already been solved with the estimated and planned count.
We just need to disable the
Prefer: count=exact
. We can do this with a config option.The text was updated successfully, but these errors were encountered: