You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[YSQL] Batch nested loops closing connection when querying information_schema table due to invalid cumulative relations when getting batched clauses
#15878
Closed
mislam-yb opened this issue
Jan 30, 2023
· 0 comments
This error occured for the latest debug build for 2.17.2.0, and was reproduced by @tanujnay112.
Reproduction:
set yb_bnl_batch_size = 1;
select table_name, table_schema from information_schema.tables;
-- works fine
set yb_bnl_batch_size = 2;
select table_name, table_schema from information_schema.tables;
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.
The text was updated successfully, but these errors were encountered:
Summary: 12e23ad introduced the concept of yb_availBatchedRelids in the PlannerRoot structure. This field is meant to be added to in the creation of a batched nested loop join node in order for its inner side to use it. It should be restored to its original state after the inner side is built and this change corrects that.
Test Plan: ./yb_build.sh release --java-test 'org.yb.pgsql.TestPgRegressJoin'
Reviewers: mtakahara
Reviewed By: mtakahara
Subscribers: yql
Differential Revision: https://phabricator.dev.yugabyte.com/D22583
mislam-yb
changed the title
[YSQL] Batch nested loops closing connection when querying information_schema table
[YSQL] Batch nested loops closing connection when querying information_schema table due to invalid cumulative relations when getting batched clauses
Feb 16, 2023
Jira Link: DB-5284
Description
When using batched nested loops, queries to
information_schema
cause the connection to close due to the following error seen on the postgres logs:This error occured for the latest debug build for 2.17.2.0, and was reproduced by @tanujnay112.
Reproduction:
The text was updated successfully, but these errors were encountered: