Skip to content

savepoint forget hook#2252

Merged
jussisaurio merged 3 commits into
mainfrom
savepoint-forget-hook
Jul 1, 2026
Merged

savepoint forget hook#2252
jussisaurio merged 3 commits into
mainfrom
savepoint-forget-hook

Conversation

@jussisaurio

Copy link
Copy Markdown
Contributor

No description provided.

@jussisaurio jussisaurio marked this pull request as ready for review July 1, 2026 07:34

@sivukhin sivukhin 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.

If this is eps-effort - should we ask clanker to write simple tests which will check that savepoint methods will be called in some expected order for some statements?

nNew = iSavepoint + (( op==SAVEPOINT_RELEASE ) ? 0 : 1);
for(ii=nNew; ii<pPager->nSavepoint; ii++){
sqlite3BitvecDestroy(pPager->aSavepoint[ii].pInSavepoint);
if( pagerUseWal(pPager)

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.

Is it bit more safer to cal xSavepointForget before any destruction from SQLite? Just worry that if SQLite will add some sqlite3DataDestroy(pPager->aSavepoint[ii].aWalData) later here - we will screw up with ordering

@jussisaurio jussisaurio merged commit 6f451a1 into main Jul 1, 2026
19 of 20 checks passed
@jussisaurio jussisaurio deleted the savepoint-forget-hook branch July 1, 2026 14:05
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