Skip to content
New issue

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

roachtest: update regression.diffs #135313

Merged
merged 1 commit into from
Dec 7, 2024
Merged

roachtest: update regression.diffs #135313

merged 1 commit into from
Dec 7, 2024

Conversation

mw5h
Copy link
Contributor

@mw5h mw5h commented Nov 15, 2024

Updated the regression.diffs file to reflect changes due to improved TRIGGER and collation support. Filed issues for the panic and trigger misbehavior.

Fixes: #132515
Informs: #135311
Informs: #135131

Release note: None

@mw5h mw5h requested a review from a team as a code owner November 15, 2024 19:01
@mw5h mw5h requested review from srosenberg and vidit-bhat and removed request for a team November 15, 2024 19:02
Copy link

blathers-crl bot commented Nov 15, 2024

Your pull request contains more than 1000 changes. It is strongly encouraged to split big PRs into smaller chunks.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Member

@yuzefovich yuzefovich left a comment

Choose a reason for hiding this comment

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

We should preserve _version_ markers that were added in #131835.

Copy link
Contributor Author

@mw5h mw5h left a comment

Choose a reason for hiding this comment

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

Done.

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @srosenberg and @vidit-bhat)

Copy link
Member

@yuzefovich yuzefovich left a comment

Choose a reason for hiding this comment

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

:lgtm: with one question.

-- check dependency restrictions
ALTER TABLE main_table DROP COLUMN b;
-ERROR: cannot drop column b of table main_table because other objects depend on it
-DETAIL: trigger after_upd_b_row_trig on table main_table depends on column b of table main_table
-trigger after_upd_a_b_row_trig on table main_table depends on column b of table main_table
-trigger after_upd_b_stmt_trig on table main_table depends on column b of table main_table
-HINT: Use DROP ... CASCADE to drop the dependent objects too.
+ERROR: error executing StatementPhase stage 1 of 1 with 8 MutationType ops: relation "main_table" (649): trigger "after_upd_b_row_trig" contains unknown column "b"
Copy link
Member

Choose a reason for hiding this comment

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

Should we extract this error into a separate issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done. I filed #136918 to track this.

+ERROR: unimplemented: CREATE TRIGGER
+HINT: You have attempted to use a feature that is not yet implemented.
+See: https://go.crdb.dev/issue-v/126359/_version_
+ERROR: internal error: building declarative schema change targets for CREATE TRIGGER: runtime error: invalid memory address or nil pointer dereference
Copy link
Member

Choose a reason for hiding this comment

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

I think this bug has already been addressed in #135667, but we can update the diff on the next failure.

Copy link
Contributor Author

@mw5h mw5h left a comment

Choose a reason for hiding this comment

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

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @srosenberg, @vidit-bhat, and @yuzefovich)

-- check dependency restrictions
ALTER TABLE main_table DROP COLUMN b;
-ERROR: cannot drop column b of table main_table because other objects depend on it
-DETAIL: trigger after_upd_b_row_trig on table main_table depends on column b of table main_table
-trigger after_upd_a_b_row_trig on table main_table depends on column b of table main_table
-trigger after_upd_b_stmt_trig on table main_table depends on column b of table main_table
-HINT: Use DROP ... CASCADE to drop the dependent objects too.
+ERROR: error executing StatementPhase stage 1 of 1 with 8 MutationType ops: relation "main_table" (649): trigger "after_upd_b_row_trig" contains unknown column "b"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done. I filed #136918 to track this.

Updated the regression.diffs file to reflect changes due to improved
TRIGGER and collation support. Filed issues for the panic and trigger
misbehavior.

Fixes: cockroachdb#132515
Informs: cockroachdb#135311
Informs: cockroachdb#135131

Release note: None
@mw5h
Copy link
Contributor Author

mw5h commented Dec 7, 2024

bors r+

@craig craig bot merged commit f0d009e into cockroachdb:master Dec 7, 2024
23 checks passed
@mw5h mw5h deleted the i132515 branch December 7, 2024 22:32
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.

roachtest: pg_regress failed
3 participants