2015-03-15 20:19:04 +01:00
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
*
|
|
|
|
* lockoptions.h
|
|
|
|
* Common header for some locking-related declarations.
|
|
|
|
*
|
|
|
|
*
|
2019-01-02 18:44:25 +01:00
|
|
|
* Copyright (c) 2014-2019, PostgreSQL Global Development Group
|
2015-03-15 20:19:04 +01:00
|
|
|
*
|
|
|
|
* src/include/nodes/lockoptions.h
|
|
|
|
*
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
*/
|
|
|
|
#ifndef LOCKOPTIONS_H
|
|
|
|
#define LOCKOPTIONS_H
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This enum represents the different strengths of FOR UPDATE/SHARE clauses.
|
|
|
|
* The ordering here is important, because the highest numerical value takes
|
|
|
|
* precedence when a RTE is specified multiple ways. See applyLockingClause.
|
|
|
|
*/
|
|
|
|
typedef enum LockClauseStrength
|
|
|
|
{
|
Improve representation of PlanRowMark.
This patch fixes two inadequacies of the PlanRowMark representation.
First, that the original LockingClauseStrength isn't stored (and cannot be
inferred for foreign tables, which always get ROW_MARK_COPY). Since some
PlanRowMarks are created out of whole cloth and don't actually have an
ancestral RowMarkClause, this requires adding a dummy LCS_NONE value to
enum LockingClauseStrength, which is fairly annoying but the alternatives
seem worse. This fix allows getting rid of the use of get_parse_rowmark()
in FDWs (as per the discussion around commits 462bd95705a0c23b and
8ec8760fc87ecde0), and it simplifies some things elsewhere.
Second, that the representation assumed that all child tables in an
inheritance hierarchy would use the same RowMarkType. That's true today
but will soon not be true. We add an "allMarkTypes" field that identifies
the union of mark types used in all a parent table's children, and use
that where appropriate (currently, only in preprocess_targetlist()).
In passing fix a couple of minor infelicities left over from the SKIP
LOCKED patch, notably that _outPlanRowMark still thought waitPolicy
is a bool.
Catversion bump is required because the numeric values of enum
LockingClauseStrength can appear in on-disk rules.
Extracted from a much larger patch to support foreign table inheritance;
it seemed worth breaking this out, since it's a separable concern.
Shigeru Hanada and Etsuro Fujita, somewhat modified by me
2015-03-15 23:41:47 +01:00
|
|
|
LCS_NONE, /* no such clause - only used in PlanRowMark */
|
2015-03-15 20:19:04 +01:00
|
|
|
LCS_FORKEYSHARE, /* FOR KEY SHARE */
|
|
|
|
LCS_FORSHARE, /* FOR SHARE */
|
|
|
|
LCS_FORNOKEYUPDATE, /* FOR NO KEY UPDATE */
|
|
|
|
LCS_FORUPDATE /* FOR UPDATE */
|
|
|
|
} LockClauseStrength;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This enum controls how to deal with rows being locked by FOR UPDATE/SHARE
|
|
|
|
* clauses (i.e., it represents the NOWAIT and SKIP LOCKED options).
|
|
|
|
* The ordering here is important, because the highest numerical value takes
|
|
|
|
* precedence when a RTE is specified multiple ways. See applyLockingClause.
|
|
|
|
*/
|
|
|
|
typedef enum LockWaitPolicy
|
|
|
|
{
|
|
|
|
/* Wait for the lock to become available (default behavior) */
|
|
|
|
LockWaitBlock,
|
|
|
|
/* Skip rows that can't be locked (SKIP LOCKED) */
|
|
|
|
LockWaitSkip,
|
|
|
|
/* Raise an error if a row cannot be locked (NOWAIT) */
|
|
|
|
LockWaitError
|
|
|
|
} LockWaitPolicy;
|
|
|
|
|
Don't include heapam.h from others headers.
heapam.h previously was included in a number of widely used
headers (e.g. execnodes.h, indirectly in executor.h, ...). That's
problematic on its own, as heapam.h contains a lot of low-level
details that don't need to be exposed that widely, but becomes more
problematic with the upcoming introduction of pluggable table storage
- it seems inappropriate for heapam.h to be included that widely
afterwards.
heapam.h was largely only included in other headers to get the
HeapScanDesc typedef (which was defined in heapam.h, even though
HeapScanDescData is defined in relscan.h). The better solution here
seems to be to just use the underlying struct (forward declared where
necessary). Similar for BulkInsertState.
Another problem was that LockTupleMode was used in executor.h - parts
of the file tried to cope without heapam.h, but due to the fact that
it indirectly included it, several subsequent violations of that goal
were not not noticed. We could just reuse the approach of declaring
parameters as int, but it seems nicer to move LockTupleMode to
lockoptions.h - that's not a perfect location, but also doesn't seem
bad.
As a number of files relied on implicitly included heapam.h, a
significant number of files grew an explicit include. It's quite
probably that a few external projects will need to do the same.
Author: Andres Freund
Reviewed-By: Alvaro Herrera
Discussion: https://postgr.es/m/20190114000701.y4ttcb74jpskkcfb@alap3.anarazel.de
2019-01-15 00:54:18 +01:00
|
|
|
/*
|
|
|
|
* Possible lock modes for a tuple.
|
|
|
|
*/
|
|
|
|
typedef enum LockTupleMode
|
|
|
|
{
|
|
|
|
/* SELECT FOR KEY SHARE */
|
|
|
|
LockTupleKeyShare,
|
|
|
|
/* SELECT FOR SHARE */
|
|
|
|
LockTupleShare,
|
|
|
|
/* SELECT FOR NO KEY UPDATE, and UPDATEs that don't modify key columns */
|
|
|
|
LockTupleNoKeyExclusive,
|
|
|
|
/* SELECT FOR UPDATE, UPDATEs that modify key columns, and DELETE */
|
|
|
|
LockTupleExclusive
|
|
|
|
} LockTupleMode;
|
|
|
|
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-21 21:18:54 +02:00
|
|
|
#endif /* LOCKOPTIONS_H */
|