Skip to content

fix: explicitly set encoding to UTF8 on embedded postgres #16604

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 18, 2025

Conversation

hugodutka
Copy link
Contributor

Fixes #16228.

I've verified that the setting does not affect existing databases.

Copy link
Member

@mafredri mafredri left a comment

Choose a reason for hiding this comment

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

👍

@hugodutka hugodutka merged commit 5e96fb5 into main Feb 18, 2025
32 checks passed
@hugodutka hugodutka deleted the hugodutka/embedded-postgres-encoding branch February 18, 2025 14:29
@github-actions github-actions bot locked and limited conversation to collaborators Feb 18, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Built-in Postgres does not use UTF8 encoding on Windows
2 participants