Question: Recommended Npgsql / EF Core connection string options for Nile DB? #867
Unanswered
EquineSolutions
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team,
We are using C# with Entity Framework Core and Npgsql to connect to Nile DB. Because Nile acts as a connection proxy, the default Npgsql behaviors cause a few protocol mismatch errors, specifically:
A ParseComplete crash during initial connection type loading.
0A000: DISCARD is not supported when EF Core closes connections or runs migrations.
To bypass these errors and get the application running, we appended the following parameters to our connection string:
Plaintext
Pooling=false;
Multiplexing=false;
Max Auto Prepare=0;
Server Compatibility Mode=NoTypeLoading;
No Reset On Close=true;
While this successfully prevents the crashes, we want to ensure we aren't introducing performance anti-patterns or missing better configuration options.
Questions:
Are these the officially recommended connection string parameters for connecting to Nile DB via Npgsql?
Are there any other EF Core or Npgsql-specific settings we should configure for optimal performance, connection pooling, and tenant isolation?
Thanks in advance for the guidance!
Beta Was this translation helpful? Give feedback.
All reactions