Azure PostgreSQL Flexible Server creation needs to set max_connections in addition to max_prepared_transactions

[AWSmith0216]

Terraform Version Details

1.10.5

Terraform Variable File Details

Not relevant

Steps to Reproduce

Create a PostgreSQL flexible server. Using the most basic input is sufficient:

postgres_servers = {
  default = {},
}

Expected Behavior

That the server parameters include the SAS documented requirements of max_connections and max_prepared_transactions both set to at least 1024. Refer to documentation:

https://helpcenter.unx.sas.com/test/doc/en/itopscdc/v_061/itopssr/p05lfgkwib3zxbn1t6nyihexp12n.htm#p1wq8ouke3c6ixn1la636df9oa1u

Actual Behavior

Only max_prepared_transactions is set, not max_connections. This is because the following portions of locals.tf only specifies max_prepared_transactions:

viya4-iac-azure/locals.tf

Line 26 in 00d33fd

default_postgres_configuration = [{ name : "max_prepared_transactions", value : 1024 }]

Additional Context

No response

References

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[Carus11]

I believe it is this way because of past restrictions on setting the max_connections parameter. It used to be tied to the instance size (it may be a holdover from the days before flexible pgserver).

While it is now automatically calculated based on the instance size, it appears like it could be changed despite the giant red box on this page:
https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-limits

Its probably worth testing out if terraform can set this value when creating a new postgresql server, or if the azure auto-calculation of max connections would win out in the end.

[github-actions]

This issue is stale because it has been open 30 days with no activity.