Skip to content

user pool_size takes precedence over database pool_size.#781

Merged
levkk merged 3 commits intopgdogdev:mainfrom
meetcleo:fix-order-of-max-database-config
Feb 19, 2026
Merged

user pool_size takes precedence over database pool_size.#781
levkk merged 3 commits intopgdogdev:mainfrom
meetcleo:fix-order-of-max-database-config

Conversation

@mijoharas
Copy link
Contributor

User is more specific, and you have multiple users per database, so it's kinda surprising that the database pool size takes precedence.

Fix that.

This one caught us out, I'm assuming it's not intentional? if so, it's a bit confusing and maybe the docs should outline that? (I still think it should be changed though.)

User is more specific, and you have multiple users per database, so it's kinda
surprising that the database pool size takes precedence.

Fix that.
@codecov
Copy link

codecov bot commented Feb 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@mijoharas mijoharas force-pushed the fix-order-of-max-database-config branch from 107c3aa to 546fab2 Compare February 19, 2026 16:05
@levkk
Copy link
Collaborator

levkk commented Feb 19, 2026

It was not intentional, and kind of became the norm since changing this is breaking. And that's fine. I'll put a note in the release notes, because this is the right way to handle it.

Could you quickly take a look at any other settings we set there and make sure user overrides database there as well? Then we can merge. I can update the docs (or if you're willing to make a PR there as well).

Thank you!

@mijoharas
Copy link
Contributor Author

hold up, saw some other ones, let me fix them too. (glad I still had the file open in my editor)

@mijoharas
Copy link
Contributor Author

Alright, should have it all now. (I simplified the statement_timeout branching a little, otherwise everything is a mechanical user/database swap).

}

#[test]
fn test_user_takes_precedence_over_database() {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Not a terrible idea to do the other configs too. Only the paranoid survive, something something

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good call, let me do that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ok had a meeting but just got back to it. Have pushed the extra test commit.

@levkk
Copy link
Collaborator

levkk commented Feb 19, 2026

Okay let's see if the tests catch anything. If we're all green, we know are tests don't cover enough! 😆

@mijoharas
Copy link
Contributor Author

Okay let's see if the tests catch anything. If we're all green, we know are tests don't cover enough! 😆

hahaha, they were when I ran them locally 😅

Copy link
Collaborator

@levkk levkk left a comment

Choose a reason for hiding this comment

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

🚀

@levkk levkk merged commit 0428df0 into pgdogdev:main Feb 19, 2026
7 checks passed
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.

2 participants

Comments