-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
pgwire: empty query should result in emptyresponse, not error/commandcomplete #9093
Comments
Huh, I thought I fixed this a long time ago, and we even have a test for it: |
@fishcakez could you give more details about how you isolated this specific issue in your use case? |
The reference issue seems to refer to using the simple |
@mjibson any chance to pull that fix soon ? |
I'm waiting on lib/pq#500 to get merged (which I don't control), otherwise we can't write a test for this. Sorry for the delay. @tamird do you have write access to lib/pq? Would you be willing to review + merge that PR? |
Sadly I do not have commit over there. On Tue, Sep 20, 2016 at 2:03 PM, Matt Jibson notifications@github.com
|
Found by @fishcakez in #5582 (comment):
An empty query will fail with an error, postgresql handles this with an EmptyQueryResponse message, instead of CommandComplete. This may not matter to cockroach.
Note that this is may appear to be a dup of #3852 but the fix to that issue didn't change what happens for empty queries.
The text was updated successfully, but these errors were encountered: