Skip to content

Add a flag for table access method to force exclusive write #969

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gfphoenix78
Copy link
Contributor

This commit adds a flag in table access method to force exclusive write. The feature allows writing of a table, i.e. insert/delete/ update, to be not concurrently safe.

What does this PR do?

Type of Change

  • Bug fix (non-breaking change)
  • New feature (non-breaking change)
  • Breaking change (fix or feature with breaking changes)
  • Documentation update

Breaking Changes

Test Plan

  • Unit tests added/updated
  • Integration tests added/updated
  • Passed make installcheck
  • Passed make -C src/test installcheck-cbdb-parallel

Impact

Performance:

User-facing changes:

Dependencies:

Checklist

Additional Context

CI Skip Instructions


@yjhjstz
Copy link
Member

yjhjstz commented Feb 27, 2025

what's scenario need ?

@gfphoenix78
Copy link
Contributor Author

what's scenario need ?

Concurrently INSERT/DELETE/UPDATE tuples in a table is considered safe in heap/AO/CO. But it's not always true. For some implementations, concurrently write that is unsafe requires to hold a big lock for exclusive write.

This commit adds a flag in table access method to force exclusive
write. The feature allows writing of a table, i.e. insert/delete/
update, to be not concurrently safe.
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.

3 participants