Update supautils.conf.j2 | added deadlock_timeout

[TheOtherBrian1]

What kind of change does this PR introduce?

supautils update

What is the current behavior?

deadlock_timeout is not configurable

What is the new behavior?

Allow users to configure deadlock_timeout

Additional context

I personally haven't come across a user with a significant deadlock problem, but Postgres.ai wrote an article outlining how changing the setting at the session level can help detect certain migration issues

Summary by CodeRabbit

• Chores
  • Updated database configuration to allow the privileged role to manage deadlock timeout settings, enabling enhanced control over query timeout behavior and performance monitoring.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A single PostgreSQL configuration template was updated to add deadlock_timeout to the list of configurations that the privileged role is allowed to modify. The parameter was inserted after auto_explain.* while preserving all other existing entries.

Changes

Cohort / File(s)	Summary
PostgreSQL Configuration Update ansible/files/postgresql_config/supautils.conf.j2	Added deadlock_timeout to the supautils.privileged_role_allowed_configs parameter, positioning it immediately after auto_explain.* in the comma-separated configuration list

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A timeout for deadlocks is quite the sweet treat,
One parameter added, the config's complete!
In supautils it nestles, a privilege renewed,
Database harmony gently ensued. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: updating supautils.conf.j2 and adding deadlock_timeout to the allowed configurations.
Description check	✅ Passed	The description follows the template structure with appropriate sections (What kind of change, current behavior, new behavior, additional context) and provides clear context for the change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch TheOtherBrian1-patch-1

---

📜 Recent review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dfbdf86 and c9b47fc.

📒 Files selected for processing (1)

• ansible/files/postgresql_config/supautils.conf.j2 (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: nix-eval / eval

🔇 Additional comments (1)

ansible/files/postgresql_config/supautils.conf.j2 (1)

13-13: LGTM! The addition of deadlock_timeout is appropriate and correctly placed.

The parameter requires superuser privileges or explicit SET privilege to change, making it a valid inclusion in the privileged role allowed configs list. The alphabetical placement is correct.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}