Skip to content

feat(pgbouncer): add m8g instance memory - #1694

Closed
TylerHillery wants to merge 1 commit into
masterfrom
tyler/chore/pgbouncer-m8g
Closed

TylerHillery wants to merge 1 commit into
masterfrom
tyler/chore/pgbouncer-m8g

Conversation

@TylerHillery

Copy link
Copy Markdown
Contributor

What kind of change does this PR introduce?

Chore

What is the current behavior?

get_instance_memory_gb() in the entrypoint for PgBouncer doesn't have m8g family instances

What is the new behavior?

Added them

Additional context

@TylerHillery
TylerHillery requested a review from a team as a code owner November 11, 2026 20:57
Copilot AI balanced review requested due to automatic review settings November 11, 2026 20:57

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are reported for the M8g instance memory-mapping change.

No open issues 🎉

What changed in this PR

Adds M8g instance memory mappings to PgBouncer’s entrypoint so these instances use known memory values instead of falling back to local defaults.

Changes:

  • Adds nine M8g sizes, from db.m8g.large through db.m8g.48xlarge, with memory values from 8 to 768 GB.
File Description
.docker/​pgbouncer/​entrypoint.sh Adds M8g mappings to get_instance_memory_gb().

Review effort: Balanced

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review found no issues

No high-confidence issues detected in this change.

@TylerHillery TylerHillery changed the title chore(pgbouncer): add m8g instance memory feat(pgbouncer): add m8g instance memory Nov 11, 2026
@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 43099076507

Coverage remained the same at 87.646%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 16094
Covered Lines: 14547
Line Coverage: 90.39%
Relevant Branches: 10214
Covered Branches: 8511
Branch Coverage: 83.33%
Branches in Coverage %: Yes
Coverage Strength: 1357.45 hits per line

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants