-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
CockroachDB doesn't return ErrorResponse if client sends a startup message with invalid database name #109992
Comments
Hello, I am Blathers. I am here to help you get the issue triaged. Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here. I was unable to automatically find someone to ping. If we have not gotten back to your issue within a few business days, you can try the following:
🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
Let's add a test for this in pkg/sql/pgwire/testdata/pgtest - let me know if you need help with the syntax for these tests. |
@giangpham712 I see the correct behaviour if the start-up message has a bad database name:
Are you relying on the implicit database name behaviour from: https://www.postgresql.org/docs/current/protocol-message-formats.html (see Startup Message) |
Workaround for CockroachDB issue that doesn't return error when database name is invalid cockroachdb/cockroach#109992
Workaround for CockroachDB issue that doesn't return error when database name is invalid cockroachdb/cockroach#109992
@giangpham712 Can you share the connection string for when this happens? Trying to figure out where things are going off the rails |
@fqazi It could be something like this
|
@fqazi maybe this related to mixed-case names specifically? |
Workaround for CockroachDB issue that doesn't return error when database name is invalid cockroachdb/cockroach#109992
No, case sensitivity also works fine if I try this in the pg_wire tests for CRDB. Let me try using Npgsql and seeing if that exhibits this problem |
@giangpham712 I tried the following sequence and still see the correct error in .NET (i.e. invalid database names error out correctly):
|
Describe the problem
With PosgreSQL, when client sends a startup message with invalid database name, the response will be ErrorResponse as specified here (https://www.postgresql.org/docs/current/protocol-flow.html). CockroachDB still returns a ReadyForQuery response
Additional context
This affects efcore.pg tests
@fqazi
Jira issue: CRDB-31206
The text was updated successfully, but these errors were encountered: