fix(server): bump bodyLimit to 3MB default allow parameterize

[avallete]

What kind of change does this PR introduce?

• Introduce PG_META_MAX_BODY_LIMIT_MB env variable to make easier parameterization
• Bump the default bodyLimit value from 1MB to 3MB.

[coveralls]

Pull Request Test Coverage Report for Build 16441335951

Details

• 9 of 10 (90.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.002%) to 76.119%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/server/constants.ts	2	3	66.67%

Totals
Change from base Build 16233676980:	0.002%
Covered Lines:	5186
Relevant Lines:	6728

---

💛 - Coveralls

[soedirgo]

What’s the context around parameterization?

[avallete]

What’s the context around parameterization?

Just a way to bump it up without needing a new release if we see that some of dashboard crafted queries still fail. Went with the 3MB default based on the few sampling I've made, but it might require further tweaking down the line.

[soedirgo]

Can you share the full context? Which dashboard queries were failing? Have they always failed or was this a recent issue?

[avallete]

Sure ! Sorry I though linear would automatically attach the issue with the PR, more context can be found here: PGMETA-60

The issue was there for a while even if in low volume (~1.2k/90 days according to sentry). I don't get the exact query that fail on the traces, but I can see that some of those events have the x-pg-application-header set to supabase/dashboard which indicate that's a query that we forge (the ones from the users are marked with supbase/dashboard-query-editor).

[soedirgo]

Gotcha thanks! Lgtm