We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When executing a query on any table with more than 128 rows, such as:
SELECT * FROM pg_class LIMIT 129;
The result is split into multiple segments, as shown below:
oid | relname | relnamespace | reltype | reloftype | relowner | relam | relfilenode | reltablespace | relpages | reltuples | relallvisible | reltoastrelid | relhasindex | relisshared | relpersistence | relkind | relnatts | relchecks | relhasrules | relhastriggers | relhassubclass | relrowsecurity | relforcerowsecurity | relispopulated | relreplident | relispartition | relrewrite | relfrozenxid | relminmxid | relacl | reloptions | relpartbound -------+-----------------------------------------------+--------------+---------+-----------+----------+-------+-------------+---------------+----------+-----------+---------------+---------------+-------------+-------------+----------------+---------+----------+-----------+-------------+----------------+----------------+----------------+---------------------+----------------+--------------+----------------+------------+--------------+------------+--------+------------+-------------- ---- (128 rows) oid | relname | relnamespace | reltype | reloftype | relowner | relam | relfilenode | reltablespace | relpages | reltuples | relallvisible | reltoastrelid | relhasindex | relisshared | relpersistence | relkind | relnatts | relchecks | relhasrules | relhastriggers | relhassubclass | relrowsecurity | relforcerowsecurity | relispopulated | relreplident | relispartition | relrewrite | relfrozenxid | relminmxid | relacl | reloptions | relpartbound ------+-------------------+--------------+---------+-----------+----------+-------+-------------+---------------+----------+-----------+---------------+---------------+-------------+-------------+----------------+---------+----------+-----------+-------------+----------------+----------------+----------------+---------------------+----------------+--------------+----------------+------------+--------------+------------+--------+------------+-------------- 2660 | pg_cast_oid_index | 11 | 0 | 0 | 10 | 403 | 2660 | 0 | 2 | 229 | 0 | 0 | f | f | p | i | 1 | 0 | f | f | f | f | f | t | n | f | 0 | 0 | 0 | | | (1 row)
This segmentation behavior disrupts the continuity of the result set, making it harder to process or view the data consistently.
The text was updated successfully, but these errors were encountered:
to #316 fix: add HasSentRowDesc to make sure we only send the Row Des…
7fd7bc3
…c once per statement.
to #316 fix: move initial data into .csv file.
7cb3cca
to #316 merge main
5a14397
TianyuZhang1214
No branches or pull requests
When executing a query on any table with more than 128 rows, such as:
The result is split into multiple segments, as shown below:
This segmentation behavior disrupts the continuity of the result set, making it harder to process or view the data consistently.
The text was updated successfully, but these errors were encountered: