-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: copy/bank/rows=10000000,nodes=9,txn=true failed #45489
Comments
(roachtest).copy/bank/rows=10000000,nodes=9,txn=true failed on release-19.1@d651c17d58e4ce97477e2fa66d04487e9039c1fd:
More
Artifacts: /copy/bank/rows=10000000,nodes=9,txn=true
See this test on roachdash |
I broke this in 03c3a7c. Fixing. |
(roachtest).copy/bank/rows=10000000,nodes=9,txn=true failed on release-19.1@f19baa3c4a1ce8c9b87842d0187e626aed5d4fb7:
More
Artifacts: /copy/bank/rows=10000000,nodes=9,txn=true
See this test on roachdash |
45712: sql: prevent arbitrary writes to system.comments r=RichardJCai a=knz Fixes #45707. Previously, the GRANT, UPDATE, DELETE and INSERT privileges were granted to `public`, i.e. everyone, on `system.comments`. This was unintended - only users with permissions on an object should be able to modify that object's comments. This patch fixes it. Release note (security update): Any user could previously modify any database/table/view/index comment via direct SQL updates to `system.comments`. This was unintended and a form of privilege escalation, and is now prevented. The privileges required for the COMMENT statement and `pg_description`, `col_description()`, `obj_description()` and `shobj_description()` are operating as in PostgreSQL and unaffected by this change: all users can *view* any comments on any object (bypassing other privileges), but modifying comments require write privilege on the target object. 45729: roachtest: fix copy/bank roachtest on 19.1 r=nvanbenschoten a=ajwerner In 19.2 we changed the name of the column from SHOW ZONE CONFIGURATION from `config_sql` to `raw_config_sql`. I relied on this column name in #45451. This change updates the test to fall back to the old defaults if the column does not exist. Fixes #45489. Release note: None Co-authored-by: Raphael 'kena' Poss <[email protected]> Co-authored-by: Andrew Werner <[email protected]>
(roachtest).copy/bank/rows=10000000,nodes=9,txn=true failed on release-19.1@1fcf7104d19c5c7634cfb52c4302bc9e70c4b9ea:
More
Artifacts: /copy/bank/rows=10000000,nodes=9,txn=true
Related:
roachtest: copy/bank/rows=10000000,nodes=9,txn=true failed #45380 roachtest: copy/bank/rows=10000000,nodes=9,txn=true failed C-test-failure O-roachtest O-robot branch-provisional_202002240854_v20.1.0-beta.2 release-blocker
roachtest: copy/bank/rows=10000000,nodes=9,txn=true failed #45297 roachtest: copy/bank/rows=10000000,nodes=9,txn=true failed C-test-failure O-roachtest O-robot branch-45179 release-blocker
roachtest: copy/bank/rows=10000000,nodes=9,txn=true failed #45058 roachtest: copy/bank/rows=10000000,nodes=9,txn=true failed C-test-failure O-roachtest O-robot branch-44941 release-blocker
roachtest: copy/bank/rows=10000000,nodes=9,txn=true failed #27688 roachtest: copy/bank/rows=10000000,nodes=9,txn=true failed A-kv-client C-test-failure O-robot branch-master
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: