Skip to content

Fix subselect_gp2 intermittent failure due to parallel test conflict#1841

Open
gfphoenix78 wants to merge 1 commit into
apache:mainfrom
gfphoenix78:fix-subselect_gp2
Open

Fix subselect_gp2 intermittent failure due to parallel test conflict#1841
gfphoenix78 wants to merge 1 commit into
apache:mainfrom
gfphoenix78:fix-subselect_gp2

Conversation

@gfphoenix78

@gfphoenix78 gfphoenix78 commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

subselect_gp and subselect_gp2 run in the same parallel test group. subselect_gp dropped and recreated tables named subselect_t1/t2, which are also created by subselect_gp2. The race caused subselect_gp2's SELECT to fail with "relation does not exist" after a successful INSERT.

Rename the tables in subselect_gp2 to subselect_gp2_t1/t2 to eliminate the naming conflict. Update all copies of the test across regress, singlenode_regress, vectorization, and pax_storage test suites.

Fixes #ISSUE_Number

What does this PR do?

Type of Change

  • Bug fix (non-breaking change)
  • New feature (non-breaking change)
  • Breaking change (fix or feature with breaking changes)
  • Documentation update

Breaking Changes

Test Plan

  • Unit tests added/updated
  • Integration tests added/updated
  • Passed make installcheck
  • Passed make -C src/test installcheck-cbdb-parallel

Impact

Performance:

User-facing changes:

Dependencies:

Checklist

Additional Context

CI Skip Instructions


subselect_gp and subselect_gp2 run in the same parallel test group.
subselect_gp dropped and recreated tables named subselect_t1/t2, which
are also created by subselect_gp2. The race caused subselect_gp2's
SELECT to fail with "relation does not exist" after a successful INSERT.

Rename the tables in subselect_gp2 to subselect_gp2_t1/t2 to eliminate
the naming conflict. Update all copies of the test across regress,
singlenode_regress, vectorization, and pax_storage test suites.

@my-ship-it my-ship-it left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants