-
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
sql: return value for indoption column doesn't have proper encoding #111907
Labels
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-community
Originated from the community
X-blathers-triaged
blathers was able to find an owner
Comments
giangpham712
added
the
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
label
Oct 6, 2023
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 have CC'd a few people who may be able to assist you:
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. |
blathers-crl
bot
added
O-community
Originated from the community
X-blathers-triaged
blathers was able to find an owner
labels
Oct 6, 2023
fqazi
added a commit
to fqazi/cockroach
that referenced
this issue
Oct 6, 2023
Previously, the indoption field inside pg_index was encoded incorrectly, which could cause problems for binary clients. Specifically, an int8 was being sent across the wire, then int2vectors are supposed to be made of int2. To address this, this patch ensures that an int2 is used and adds assertion inside the conversion code (for int2vector) to avoid future problems. Fixes: cockroachdb#111907 Release note (bug fix): indoption inside pg_index was not properly encoded, causing clients to be unable to decode it as int2vector.
fqazi
added a commit
to fqazi/cockroach
that referenced
this issue
Oct 6, 2023
Previously, the indoption field inside pg_index was encoded incorrectly, which could cause problems for binary clients. Specifically, an int8 was being sent across the wire, then int2vectors are supposed to be made of int2. To address this, this patch ensures that an int2 is used and adds assertion inside the conversion code (for int2vector) to avoid future problems. Fixes: cockroachdb#111907 Release note (bug fix): indoption inside pg_index was not properly encoded, causing clients to be unable to decode it as int2vector.
craig bot
pushed a commit
that referenced
this issue
Oct 6, 2023
111911: pg_catalog: indoption was not encoded correctly r=fqazi a=fqazi Previously, the indoption field inside pg_index was encoded incorrectly, which could cause problems for binary clients. Specifically, an int8 was being sent across the wire, then int2vectors are supposed to be made of int2. To address this, this patch ensures that an int2 is used and adds assertion inside the conversion code (for int2vector) to avoid future problems. Fixes: #111907 Release note (bug fix): indoption inside pg_index was not properly encoded, causing clients to be unable to decode it as int2vector. Co-authored-by: Faizan Qazi <[email protected]>
blathers-crl bot
pushed a commit
that referenced
this issue
Oct 6, 2023
Previously, the indoption field inside pg_index was encoded incorrectly, which could cause problems for binary clients. Specifically, an int8 was being sent across the wire, then int2vectors are supposed to be made of int2. To address this, this patch ensures that an int2 is used and adds assertion inside the conversion code (for int2vector) to avoid future problems. Fixes: #111907 Release note (bug fix): indoption inside pg_index was not properly encoded, causing clients to be unable to decode it as int2vector.
blathers-crl bot
pushed a commit
that referenced
this issue
Oct 6, 2023
Previously, the indoption field inside pg_index was encoded incorrectly, which could cause problems for binary clients. Specifically, an int8 was being sent across the wire, then int2vectors are supposed to be made of int2. To address this, this patch ensures that an int2 is used and adds assertion inside the conversion code (for int2vector) to avoid future problems. Fixes: #111907 Release note (bug fix): indoption inside pg_index was not properly encoded, causing clients to be unable to decode it as int2vector.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-community
Originated from the community
X-blathers-triaged
blathers was able to find an owner
Describe the problem
In this query
The return value for
indoption
uses int64 encoding instead of int16Additional context
This affects efcore.pg tests
@fqazi
Jira issue: CRDB-32127
The text was updated successfully, but these errors were encountered: