Fix system_queries test to actually test the problem (#7613)

The test added in #7604 doesn't reach the `HasRangeTableRef` function
and thus doesn't test what it should.

Co-authored-by: Karina Litskevich <litskevichkarina@gmail.com>
pull/7669/merge
Karina 2025-02-07 17:29:13 +03:00 committed by GitHub
parent 829665ebca
commit 711aec80fa
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 6 additions and 0 deletions

View File

@ -1,3 +1,5 @@
BEGIN;
SET LOCAL citus.show_shards_for_app_name_prefixes = '';
-- The following query retrieves the foreign key constraints of the table "pg_dist_background_job" -- The following query retrieves the foreign key constraints of the table "pg_dist_background_job"
-- along with their details. This modification includes a fix for a null pointer exception that occurred -- along with their details. This modification includes a fix for a null pointer exception that occurred
-- in the "HasRangeTableRef" method of "worker_shard_visibility". The issue was resolved with PR #7604. -- in the "HasRangeTableRef" method of "worker_shard_visibility". The issue was resolved with PR #7604.
@ -31,3 +33,4 @@ order by
pg_dist_background_task_depend_job_id_fkey | job_id | pg_dist_background_job | pg_catalog pg_dist_background_task_depend_job_id_fkey | job_id | pg_dist_background_job | pg_catalog
(2 rows) (2 rows)
END;

View File

@ -1,3 +1,5 @@
BEGIN;
SET LOCAL citus.show_shards_for_app_name_prefixes = '';
-- The following query retrieves the foreign key constraints of the table "pg_dist_background_job" -- The following query retrieves the foreign key constraints of the table "pg_dist_background_job"
-- along with their details. This modification includes a fix for a null pointer exception that occurred -- along with their details. This modification includes a fix for a null pointer exception that occurred
-- in the "HasRangeTableRef" method of "worker_shard_visibility". The issue was resolved with PR #7604. -- in the "HasRangeTableRef" method of "worker_shard_visibility". The issue was resolved with PR #7604.
@ -25,3 +27,4 @@ where
and ns.nspname='pg_catalog' and ns.nspname='pg_catalog'
order by order by
fns.nspname, fc.relname, a.attnum; fns.nspname, fc.relname, a.attnum;
END;