How to increase max_stack_depth server parameter for an Azure PostgreSQL Flexible Server.?

Question

How to increase max_stack_depth server parameter for an Azure PostgreSQL Flexible Server?

The parameter is read only. I defaults to 2048 kB for any sku I've seen so far (B2s, D2ds_v4/5, D4s_v3), therefore doesn't look to be related to the compute size for those smaller tiers.

And there is no option to increase the parameter by ourselves or thru a support request.

We currently hit the limitation while migrating complex recursive stored procedures from Oracle to PostgreSQL and ideally want to avoid a complete rewrite of the corresponding code.

Any pointers appreciated!

Update 2025-10-10
As part of the further investigations, it recently turned out, that there was a problem in the data itself.

Basically wrong test data in a processed table, resulting in a cycle of a processed parent-child hierarchy. Which also was present in the Oracle source, but less obvious due to different client fetch limits resulting in not reaching the cycle.

After fixing the data, we haven't hit the max_stack_depth parameter limit again and everything is working fine now. Recursion works for the required levels without any refactoring of the code in Azure PostgreSQL Server, too.

=> therefore we're good with the default max_stack_depth 2048 kB

Answer 1

Hi Johann Hackl
In Azure Database for PostgreSQL – Flexible Server, the max_stack_depth parameter is read-only and cannot be changed by users or through a support request. It is fixed at 2 MB (2048 kB) across SKUs and is not tied to compute size.

This limitation exists because the parameter directly affects memory allocation and stability at the service level, so Azure enforces a fixed safe default.

If your workload is hitting this ceiling (e.g., when migrating recursive stored procedures from Oracle), the main options are:

• Refactor recursive logic to be less deep (e.g., iterative approaches where possible).
• Break down complex stored procedures into smaller sub-procedures with controlled stack usage.
• Evaluate alternative approaches such as using Common Table Expressions (CTEs) with iteration where recursion is not essential.

Unfortunately, there’s currently no way to override or increase max_stack_depth in Azure Database for PostgreSQL Flexible Server. If this limitation is a blocker for your migration, I would recommend sharing feedback via Azure Feedback so the product team can consider it in future updates. Hope this helps. Do let us know if you any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.