Skip to content

Do not set max_memory if given the empty string#614

Merged
JelteF merged 1 commit intomainfrom
dont-set-max_memory-if-empty
Feb 18, 2025
Merged

Do not set max_memory if given the empty string#614
JelteF merged 1 commit intomainfrom
dont-set-max_memory-if-empty

Conversation

@JelteF
Copy link
Copy Markdown
Collaborator

@JelteF JelteF commented Feb 18, 2025

This was already the intended behaviour, as the already existing NULL check shows. The value of a GUC is never NULL though, but can be an empty string. This keeps the NULL check for safety purposes.

This was already the intended behaviour, as the already existing NULL
check shows. The value of a GUC is never NULL though, but can be an
empty string. This keeps the NULL check for safety purposes.
@JelteF JelteF merged commit 82d3a0f into main Feb 18, 2025
@JelteF JelteF deleted the dont-set-max_memory-if-empty branch February 18, 2025 13:30
JelteF added a commit that referenced this pull request Mar 13, 2025
I made dumb mistake in #614. I accidentally checked the opposite of what
intended to check. This fixes that and adds a test to confirm that the
new behaviour is now correct.
JelteF added a commit that referenced this pull request Mar 13, 2025
I made dumb mistake in #614. I accidentally checked the opposite of what
intended to check. This fixes that and adds a test to confirm that the
new behaviour is now correct.
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