-
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: support extended protocol binary format for Geometry/Geography/Box2D types #81066
Labels
A-sql-pgwire
pgwire protocol issues.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-sentry
Originated from an in-the-wild panic report.
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Comments
cockroach-teamcity
added
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-sentry
Originated from an in-the-wild panic report.
labels
May 5, 2022
yuzefovich
changed the title
sentry: encoding.go:797: error in argument for ×: unsupported OID 90000 with format code FormatBinary
--
*errutil.leafError: unsupported OID 90000 with format code FormatBinary (1)
encoding.go:797: *withstack...
sql: v21.1.7: unsupported OID 90000 with format code FormatBinary
May 16, 2022
blathers-crl
bot
added
the
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
label
May 16, 2022
We definitely don't implement the binary protocol for spatial. We probably should. Looks like it's a sent/received using WKB/EWKB: |
otan
changed the title
sql: v21.1.7: unsupported OID 90000 with format code FormatBinary
sql: support extended protocol for Geometry/Geography types
May 16, 2022
otan
changed the title
sql: support extended protocol for Geometry/Geography types
sql: support extended protocol for Geometry/Geography/Box2D types
May 16, 2022
rafiss
changed the title
sql: support extended protocol for Geometry/Geography/Box2D types
sql: support extended protocol binary format for Geometry/Geography/Box2D types
Oct 12, 2022
This was referenced Nov 3, 2022
In this comment @carstenpiepel said:
|
This was referenced Dec 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-sql-pgwire
pgwire protocol issues.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-sentry
Originated from an in-the-wild panic report.
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
This issue was autofiled by Sentry. It represents a crash or reported error on a live cluster with telemetry enabled.
Sentry link: https://sentry.io/organizations/cockroach-labs/issues/3252603016/?referrer=webhooks_plugin
Panic message:
Stacktrace (expand for inline code snippets):
cockroach/pkg/sql/conn_executor_prepare.go
Lines 386 to 388 in 1fac61a
cockroach/pkg/sql/conn_executor.go
Lines 1626 to 1628 in 1fac61a
cockroach/pkg/sql/conn_executor.go
Lines 1449 to 1451 in 1fac61a
cockroach/pkg/sql/conn_executor.go
Lines 483 to 485 in 1fac61a
cockroach/pkg/sql/pgwire/conn.go
Lines 627 to 629 in 1fac61a
/usr/local/go/src/runtime/asm_amd64.s#L1373-L1375 in runtime.goexit
v21.1.7
Jira issue: CRDB-15368
Epic CRDB-17785
The text was updated successfully, but these errors were encountered: