Skip to content

feat: 6/7 preserve SET ROLE in simulation replay#25526

Open
tabVersion wants to merge 1 commit intoralph/rbac-split-05-frontend-role-dispatch-cachefrom
ralph/rbac-split-06-set-role-session-semantics
Open

feat: 6/7 preserve SET ROLE in simulation replay#25526
tabVersion wants to merge 1 commit intoralph/rbac-split-05-frontend-role-dispatch-cachefrom
ralph/rbac-split-06-set-role-session-semantics

Conversation

@tabVersion
Copy link
Copy Markdown
Contributor

Stack: 6/7 for splitting ralph/rbac-postgres-final-alignment onto origin/main.

Base: ralph/rbac-split-05-frontend-role-dispatch-cache
Next: ralph/rbac-split-07-pg-catalog-compatibility

Scope

  • Preserve session-level SET ROLE replay across simulation reconnects.
  • Ignore transaction-local role changes and clear replay state on RESET ROLE / SET ROLE NONE.

Out of scope

  • pg_catalog compatibility and SLT snapshots.

Tests

  • cargo fmt --check
  • cargo check -p risingwave_simulation

@tabVersion tabVersion changed the title rbac: preserve SET ROLE in simulation replay feat: 6/7 preserve SET ROLE in simulation replay Apr 28, 2026
@github-actions github-actions Bot added type/feature Type: New feature. and removed Invalid PR Title labels Apr 28, 2026
The simulation client now tracks session-level SET ROLE statements across reconnects while intentionally ignoring SET LOCAL ROLE and clearing the replay state on RESET ROLE or SET ROLE NONE.\n\nConstraint: Restart/reconnect simulation should preserve session role state without leaking transaction-local role changes.\nConfidence: high\nScope-risk: narrow\nTested: cargo fmt --check; cargo check -p risingwave_simulation\nNot-tested: Full simulation integration suite
@tabVersion tabVersion force-pushed the ralph/rbac-split-06-set-role-session-semantics branch from 8559414 to 0940e03 Compare May 8, 2026 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type/feature Type: New feature.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant