Skip to content

Fixed bug #9319 : READ COMMITTED READ CONSISTENCY: transaction memory grows by about 200 bytes per executed DML statement until COMMIT - #9326

Merged
hvlad merged 2 commits into
v5.0-releasefrom
work/gh-9319
Nov 21, 2026
Merged

hvlad merged 2 commits into
v5.0-releasefrom
work/gh-9319

Conversation

@hvlad

@hvlad hvlad commented Nov 20, 2026

Copy link
Copy Markdown
Member

Move list of free VerbAction's into transaction.

… grows by about 200 bytes per executed DML statement until COMMIT

Move list of free VerbAction's into transaction.
@aafemt

aafemt commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

VerbAction and its members are allocated from transaction pool. Is there a reason to delete them explicitly in transaction destructor and not to use delete-by-pool?

…ocated from and released with transaction pool
@hvlad

hvlad commented Nov 20, 2026

Copy link
Copy Markdown
Member Author

VerbAction and its members are allocated from transaction pool. Is there a reason to delete them explicitly in transaction destructor and not to use delete-by-pool?

Ok

@hvlad
hvlad merged commit 00ed6de into v5.0-release Nov 21, 2026
46 checks passed
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.

READ COMMITTED READ CONSISTENCY: transaction memory grows by about 200 bytes per executed DML statement until COMMIT (4.0, 5.0, 6.0)

3 participants