DataGrip compatibility regression from v1.5.0 to v1.5.1

[TennyZhuang]

Describe the bug

Although we don't have official support for DataGrip, it is generally usable in v1.5.0. However, in v1.5.1, a new bug was introduced and we should fix it.

Error message/log

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

v1.5.1

Additional context

#10347

[TennyZhuang]

bisecting

0bc2da2 passed
6da9617 failed
a5ba48b failed
1ce8024 failed
a69216f failed
8914dd3 passed

[TennyZhuang]

#13999
#14015

Caused the regression

[TennyZhuang]

https://github.com/pgjdbc/pgjdbc/blob/259cbe54f852818165b7cc7dfab5c8a612eff102/pgjdbc/src/main/java/org/postgresql/core/v3/QueryExecutorImpl.java#L2334

[TennyZhuang]

query log

2023-12-20T23:33:32.378972+08:00 risingwave-main ThreadId(11) mode=(extended query execute) session=1 status=ok time=0ms sql=SHOW TRANSACTION ISOLATION LEVEL

[TennyZhuang]

import psycopg
connection = psycopg.connect(
    host="127.0.0.1",
    port=4566,
    user="root",
    password="",
    dbname="dev",
)
cursor = connection.cursor()
cursor.execute('show transaction isolation level', prepare=True)

DatabaseError: server sent data ("D" message) without prior row description ("T" message)

[TennyZhuang]

https://github.com/postgres/postgres/blob/dc212340058b4e7ecfc5a7a81ec50e7a207bf288/src/interfaces/libpq/fe-protocol3.c#L401

[TennyZhuang]

psql reproduce

dev=> show transaction isolation level; \bind \g
server sent data ("D" message) without prior row description ("T" message)
server sent data ("D" message) without prior row description ("T" message)

[TennyZhuang]

Conclusion: The BeMessage::RowDescription is generated at another place, and it's inconsistent with rows/row_desc in handler.

[sheltonsuen]

by the way, this may not only cause IDE error, spring application may also rise error when creating connection pool,
Factory method 'entityManagerFactory' threw exception with message: Failed to initialize pool: Received resultset tuples, but no field structure for them

revert to 14.0 will solve this problem

[BugenZhao]

revert to 14.0 will solve this problem

v1.5.0 should not have such issue. Would you please give it a try?

[TennyZhuang]

#14111

The fix will be included in v1.5.2 and v1.6.0.