Tracking: binary format bugs and unimplemented features

[kwannoel]

• bug(frontend): pgwire binary format for interval overflows #8041
• bug(frontend): pgwire binary response unimplemented for list and struct #7949
• bug(frontend): pgwire binary response unimplemented for byte array
• bug(frontend): pgwire binary response unimplemented for decimal inf,-inf
• bug(frontend): pgwire binary response unimplemented for JSONB type

Possible motivations/users:

• support connector-x read_sql  #7793

Please enable test cases in

risingwave/e2e_test/extended_mode/type.slt

Lines 6 to 19 in cb825f0

	# RisingWave can't support list and struct now so we skip them.
	# include ../batch/types/array.slt.part
	# include ../batch/types/struct.slt.part
	# include ../batch/types/list.slt.part
	# Sqllogitest can't support binary format bytea type so we skip it.
	# include ../batch/types/bytea.slt.part
	# Can't support inf,-inf binary format now so we skip it.
	# include ../batch/types/decimal.slt.part
	# Sqllogitest can't support binary format jsonb type so we skip it.
	# include ../batch/types/jsonb_ord.slt.part
	# include ../batch/types/jsonb.slt.part

[kwannoel]

Might be higher priority, if users query with parameters (requires extended query mode -> uses binary format) or some integrations require binary format (cr: @jon-chuang ).

https://www.postgresql.org/docs/current/protocol-overview.html#PROTOCOL-QUERY-CONCEPTS

[github-actions]

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄