Expand description
Row-lock target resolution and the physical LockRows operator.
Re-exports§
pub use context::RowLockContext;
Modules§
- context
- Capabilities required by query tuple locking, separated by state ownership.
Structs§
Functions§
- apply_
propagated_ view_ lock - Apply a row mark selected for a stored view to the view plan before execution. Stored view plans are not present when the SQL compiler pushes row marks into derived tables, so runtime expansion must perform the same propagation to ensure an outer
NOWAITorSKIP LOCKEDpolicy is merged before an inner row mark can block. - attach_
lock_ rows - lock_
explained_ relations - Hold the explained statement’s relation identities before collecting physical metadata or executing ANALYZE.
- lock_
query_ relations - Acquire
PostgreSQLAccessShareLockequivalents for every concrete table referenced by a query. The locks are transaction-scoped, so a cursor declaration keeps its bound relations alive until commit while ordinary persistent statements keep DDL from changing a source during execution. - query_
has_ row_ locks - resolve_
row_ locks - validate_
query_ row_ locks - Resolve cursor row-lock targets without opening or pulling the query.
PostgreSQLperforms these declaration-time checks even though expression evaluation and tuple locking wait until FETCH.