2015-05-15 22:03:16 +02:00
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
*
|
|
|
|
* stratnum.h
|
|
|
|
* POSTGRES strategy number definitions.
|
|
|
|
*
|
|
|
|
*
|
2018-01-03 05:30:12 +01:00
|
|
|
* Portions Copyright (c) 1996-2018, PostgreSQL Global Development Group
|
2015-05-15 22:03:16 +02:00
|
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
|
|
|
*
|
|
|
|
* src/include/access/stratnum.h
|
|
|
|
*
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
*/
|
|
|
|
#ifndef STRATNUM_H
|
|
|
|
#define STRATNUM_H
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Strategy numbers identify the semantics that particular operators have
|
|
|
|
* with respect to particular operator classes. In some cases a strategy
|
|
|
|
* subtype (an OID) is used as further information.
|
|
|
|
*/
|
|
|
|
typedef uint16 StrategyNumber;
|
|
|
|
|
|
|
|
#define InvalidStrategy ((StrategyNumber) 0)
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Strategy numbers for B-tree indexes.
|
|
|
|
*/
|
|
|
|
#define BTLessStrategyNumber 1
|
|
|
|
#define BTLessEqualStrategyNumber 2
|
|
|
|
#define BTEqualStrategyNumber 3
|
|
|
|
#define BTGreaterEqualStrategyNumber 4
|
|
|
|
#define BTGreaterStrategyNumber 5
|
|
|
|
|
|
|
|
#define BTMaxStrategyNumber 5
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Strategy numbers common to (some) GiST, SP-GiST and BRIN opclasses.
|
|
|
|
*
|
|
|
|
* The first few of these come from the R-Tree indexing method (hence the
|
|
|
|
* names); the others have been added over time as they have been needed.
|
|
|
|
*/
|
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
|
|
|
#define RTLeftStrategyNumber 1 /* for << */
|
|
|
|
#define RTOverLeftStrategyNumber 2 /* for &< */
|
|
|
|
#define RTOverlapStrategyNumber 3 /* for && */
|
|
|
|
#define RTOverRightStrategyNumber 4 /* for &> */
|
|
|
|
#define RTRightStrategyNumber 5 /* for >> */
|
|
|
|
#define RTSameStrategyNumber 6 /* for ~= */
|
|
|
|
#define RTContainsStrategyNumber 7 /* for @> */
|
|
|
|
#define RTContainedByStrategyNumber 8 /* for <@ */
|
|
|
|
#define RTOverBelowStrategyNumber 9 /* for &<| */
|
|
|
|
#define RTBelowStrategyNumber 10 /* for <<| */
|
|
|
|
#define RTAboveStrategyNumber 11 /* for |>> */
|
|
|
|
#define RTOverAboveStrategyNumber 12 /* for |&> */
|
|
|
|
#define RTOldContainsStrategyNumber 13 /* for old spelling of @> */
|
|
|
|
#define RTOldContainedByStrategyNumber 14 /* for old spelling of <@ */
|
|
|
|
#define RTKNNSearchStrategyNumber 15 /* for <-> (distance) */
|
|
|
|
#define RTContainsElemStrategyNumber 16 /* for range types @> elem */
|
|
|
|
#define RTAdjacentStrategyNumber 17 /* for -|- */
|
|
|
|
#define RTEqualStrategyNumber 18 /* for = */
|
|
|
|
#define RTNotEqualStrategyNumber 19 /* for != */
|
|
|
|
#define RTLessStrategyNumber 20 /* for < */
|
|
|
|
#define RTLessEqualStrategyNumber 21 /* for <= */
|
|
|
|
#define RTGreaterStrategyNumber 22 /* for > */
|
|
|
|
#define RTGreaterEqualStrategyNumber 23 /* for >= */
|
|
|
|
#define RTSubStrategyNumber 24 /* for inet >> */
|
|
|
|
#define RTSubEqualStrategyNumber 25 /* for inet <<= */
|
|
|
|
#define RTSuperStrategyNumber 26 /* for inet << */
|
|
|
|
#define RTSuperEqualStrategyNumber 27 /* for inet >>= */
|
2018-04-03 18:46:45 +02:00
|
|
|
#define RTPrefixStrategyNumber 28 /* for text ^@ */
|
2015-05-15 22:03:16 +02:00
|
|
|
|
2018-04-03 18:46:45 +02:00
|
|
|
#define RTMaxStrategyNumber 28
|
2015-05-15 22:03:16 +02:00
|
|
|
|
|
|
|
|
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 /* STRATNUM_H */
|