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.

Sign up for GitHub

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

Jump to bottom

Immutable table #8387

Open

EPluribusUnum opened this issue Jan 14, 2025 · 0 comments

EPluribusUnum commented Jan 14, 2025 •

edited

Loading

Hi *!

Like in Oracle : https://oracle-base.com/articles/21c/immutable-tables-21c

also add NO INSERT [LOCKED] clause.

It's for data tampering protection (for example log table).
But also using this metadata information some optimizations are possible:

better data page fill: no need to leave empty space for record version when NO DELETE LOCKED clause is used
better index tree: you can build a better tree layout when both NO DELETE LOCKED and NO INSERT LOCKED clause is used (no change at all possible)
new index type: can be use anternate indexing methods when both NO DELETE LOCKED and NO INSERT LOCKED clause is used (no change at all possible) (see Static search trees (S+) index #8388)

EPluribusUnum mentioned this issue

Static search trees (S+) index #8388

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment