Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
1a4a0329
Commit
1a4a0329
authored
Jan 10, 2020
by
Peter Geoghegan
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
nbtree: Rename BT_HEAP_TID_ATTR.
Author: Peter Geoghegan Reviewed-By: Heikki Linnakangas
parent
a0dc3c19
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
6 deletions
+5
-6
src/include/access/nbtree.h
src/include/access/nbtree.h
+5
-6
No files found.
src/include/access/nbtree.h
View file @
1a4a0329
...
@@ -263,9 +263,8 @@ typedef struct BTMetaPageData
...
@@ -263,9 +263,8 @@ typedef struct BTMetaPageData
* offset field only stores the number of columns/attributes when the
* offset field only stores the number of columns/attributes when the
* INDEX_ALT_TID_MASK bit is set, which doesn't count the trailing heap
* INDEX_ALT_TID_MASK bit is set, which doesn't count the trailing heap
* TID column sometimes stored in pivot tuples -- that's represented by
* TID column sometimes stored in pivot tuples -- that's represented by
* the presence of BT_HEAP_TID_ATTR. The INDEX_ALT_TID_MASK bit in t_info
* the presence of BT_PIVOT_HEAP_TID_ATTR. The INDEX_ALT_TID_MASK bit in
* is always set on BTREE_VERSION 4. BT_HEAP_TID_ATTR can only be set on
* t_info is always set on BTREE_VERSION 4 pivot tuples.
* BTREE_VERSION 4.
*
*
* In version 3 indexes, the INDEX_ALT_TID_MASK flag might not be set in
* In version 3 indexes, the INDEX_ALT_TID_MASK flag might not be set in
* pivot tuples. In that case, the number of key columns is implicitly
* pivot tuples. In that case, the number of key columns is implicitly
...
@@ -296,7 +295,7 @@ typedef struct BTMetaPageData
...
@@ -296,7 +295,7 @@ typedef struct BTMetaPageData
/* Item pointer offset bits */
/* Item pointer offset bits */
#define BT_RESERVED_OFFSET_MASK 0xF000
#define BT_RESERVED_OFFSET_MASK 0xF000
#define BT_N_KEYS_OFFSET_MASK 0x0FFF
#define BT_N_KEYS_OFFSET_MASK 0x0FFF
#define BT_
HEAP_TID_ATTR
0x1000
#define BT_
PIVOT_HEAP_TID_ATTR
0x1000
/* Get/set downlink block number in pivot tuple */
/* Get/set downlink block number in pivot tuple */
#define BTreeTupleGetDownLink(itup) \
#define BTreeTupleGetDownLink(itup) \
...
@@ -347,7 +346,7 @@ typedef struct BTMetaPageData
...
@@ -347,7 +346,7 @@ typedef struct BTMetaPageData
#define BTreeTupleGetHeapTID(itup) \
#define BTreeTupleGetHeapTID(itup) \
( \
( \
(itup)->t_info & INDEX_ALT_TID_MASK && \
(itup)->t_info & INDEX_ALT_TID_MASK && \
(ItemPointerGetOffsetNumberNoCheck(&(itup)->t_tid) & BT_HEAP_TID_ATTR) != 0 ? \
(ItemPointerGetOffsetNumberNoCheck(&(itup)->t_tid) & BT_
PIVOT_
HEAP_TID_ATTR) != 0 ? \
( \
( \
(ItemPointer) (((char *) (itup) + IndexTupleSize(itup)) - \
(ItemPointer) (((char *) (itup) + IndexTupleSize(itup)) - \
sizeof(ItemPointerData)) \
sizeof(ItemPointerData)) \
...
@@ -362,7 +361,7 @@ typedef struct BTMetaPageData
...
@@ -362,7 +361,7 @@ typedef struct BTMetaPageData
do { \
do { \
Assert((itup)->t_info & INDEX_ALT_TID_MASK); \
Assert((itup)->t_info & INDEX_ALT_TID_MASK); \
ItemPointerSetOffsetNumber(&(itup)->t_tid, \
ItemPointerSetOffsetNumber(&(itup)->t_tid, \
ItemPointerGetOffsetNumberNoCheck(&(itup)->t_tid) | BT_HEAP_TID_ATTR); \
ItemPointerGetOffsetNumberNoCheck(&(itup)->t_tid) | BT_
PIVOT_
HEAP_TID_ATTR); \
} while(0)
} while(0)
/*
/*
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment