Skip to content
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

Fix configuring effective_io_concurrency #6289

Merged
merged 1 commit into from Oct 12, 2023
Merged

Conversation

msullivan
Copy link
Member

Configuring actual postgres backend settings only works for nontrivial
types like duration and memory, not simple ones like int.

I think the problem was introduced by cc5958c.

Fixes edgedb/edgedb-cli#1140.

Configuring actual postgres backend settings only works for nontrivial
types like duration and memory, not simple ones like int.

I think the problem was introduced by cc5958c.

Fixes #6109.
@msullivan msullivan merged commit 9f4116f into master Oct 12, 2023
22 checks passed
@msullivan msullivan deleted the effective-io-concurrency branch October 12, 2023 23:04
msullivan added a commit that referenced this pull request Oct 13, 2023
Configuring actual postgres backend settings only works for nontrivial
types like duration and memory, not simple ones like int.

I think the problem was introduced by cc5958c.

Fixes #6109.
aljazerzen pushed a commit that referenced this pull request Oct 16, 2023
Configuring actual postgres backend settings only works for nontrivial
types like duration and memory, not simple ones like int.

I think the problem was introduced by cc5958c.

Fixes #6109.
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.

Unable to set effective_io_concurrency via CLI or REPL (InternalServerError when attempting from the REPL)
3 participants