mirror of
https://github.com/postgres/postgres.git
synced 2025-08-21 10:42:50 +03:00
Add assertions that we hold some relevant lock during relation open.
Opening a relation with no lock at all is unsafe; there's no guarantee that we'll see a consistent state of the relevant catalog entries. While use of MVCC scans to read the catalogs partially addresses that complaint, it's still possible to switch to a new catalog snapshot partway through loading the relcache entry. Moreover, whether or not you trust the reasoning behind sometimes using less than AccessExclusiveLock for ALTER TABLE, that reasoning is certainly not valid if concurrent users of the table don't hold a lock corresponding to the operation they want to perform. Hence, add some assertion-build-only checks that require any caller of relation_open(x, NoLock) to hold at least AccessShareLock. This isn't a full solution, since we can't verify that the lock level is semantically appropriate for the action --- but it's definitely of some use, because it's already caught two bugs. We can also assert that callers of addRangeTableEntryForRelation() hold at least the lock level specified for the new RTE. Amit Langote and Tom Lane Discussion: https://postgr.es/m/16565.1538327894@sss.pgh.pa.us
This commit is contained in:
@@ -28,6 +28,7 @@
|
||||
#include "parser/parse_enr.h"
|
||||
#include "parser/parse_relation.h"
|
||||
#include "parser/parse_type.h"
|
||||
#include "storage/lmgr.h"
|
||||
#include "utils/builtins.h"
|
||||
#include "utils/lsyscache.h"
|
||||
#include "utils/rel.h"
|
||||
@@ -1272,7 +1273,7 @@ addRangeTableEntry(ParseState *pstate,
|
||||
*
|
||||
* lockmode is the lock type required for query execution; it must be one
|
||||
* of AccessShareLock, RowShareLock, or RowExclusiveLock depending on the
|
||||
* RTE's role within the query. The caller should always hold that lock mode
|
||||
* RTE's role within the query. The caller must hold that lock mode
|
||||
* or a stronger one.
|
||||
*
|
||||
* Note: properly, lockmode should be declared LOCKMODE not int, but that
|
||||
@@ -1295,6 +1296,7 @@ addRangeTableEntryForRelation(ParseState *pstate,
|
||||
Assert(lockmode == AccessShareLock ||
|
||||
lockmode == RowShareLock ||
|
||||
lockmode == RowExclusiveLock);
|
||||
Assert(CheckRelationLockedByMe(rel, lockmode, true));
|
||||
|
||||
rte->rtekind = RTE_RELATION;
|
||||
rte->alias = alias;
|
||||
|
Reference in New Issue
Block a user