Skip to content

sql-227: Fix statement-logging throttling when sample rate is changed#36892

Open
SangJunBak wants to merge 2 commits into
MaterializeInc:mainfrom
SangJunBak:jun/sql-227
Open

sql-227: Fix statement-logging throttling when sample rate is changed#36892
SangJunBak wants to merge 2 commits into
MaterializeInc:mainfrom
SangJunBak:jun/sql-227

Conversation

@SangJunBak

@SangJunBak SangJunBak commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

see commit messages for details

Motivation

Fixes sql-227
etc.

@SangJunBak SangJunBak changed the title adapter: fix statement-logging throttling when sample rate is changed sql-227: Fix statement-logging throttling when sample rate is changed Jun 3, 2026
…statement execution events

In the frontend peek, we mutate mark a prepared statement as logged before the throttling check. Whileas in the original coordinator path, we wait until after. This causes a bug where if we initially throttled a statement, subsequent non-throttled executions will cause a prepared statement to never be logged in mz_prepared_statement_history
We mirror the behavior in the old coordinator statement logging where we mark it as logged after the throttle check
@SangJunBak SangJunBak requested a review from ggevay June 22, 2026 16:02
@SangJunBak SangJunBak marked this pull request as ready for review June 22, 2026 16:02
@SangJunBak SangJunBak requested a review from a team as a code owner June 22, 2026 16:02
@SangJunBak SangJunBak force-pushed the jun/sql-227 branch 2 times, most recently from db37a9c to cad37ce Compare June 22, 2026 18:27
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.

1 participant