Skip to content

Commit 4ac9e42

Browse files
author
Arseny Kositsyn
committed
[PGPRO-12159] Fixed the build on version 18 of PostgreSQL.
Tags: rum
1 parent 3f1e6cf commit 4ac9e42

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

src/rum_debug_funcs.c

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ do { \
102102
#define RumWriteResBlckNumToValues(piState, counter) \
103103
do { \
104104
(piState)->values[(counter)] = \
105-
UInt32GetDatum(PostingItemGetBlockNumber(&((piState)->curPitem))); \
105+
UInt32GetDatum(RumPostingItemGetBlockNumber(&((piState)->curPitem))); \
106106
} while(0)
107107

108108
#define RumWriteResAddInfoToValues(piState, counter) \
@@ -129,7 +129,7 @@ do { \
129129
do { \
130130
memcpy(&((piState)->curPitem), \
131131
RumDataPageGetItem((piState)->page, \
132-
(piState)->srfFctx->call_cntr), sizeof(PostingItem)); \
132+
(piState)->srfFctx->call_cntr), sizeof(RumPostingItem)); \
133133
} while(0)
134134

135135
#define RumPrepareResultTuple(piState) \
@@ -142,7 +142,7 @@ do { \
142142
} while(0)
143143

144144
#define RumPrepareCurPitemToPostingList(piState) \
145-
memset(&((piState)->curPitem), 0, sizeof(PostingItem))
145+
memset(&((piState)->curPitem), 0, sizeof(RumPostingItem))
146146

147147
/*
148148
* This is necessary in order for the prepare_scan()
@@ -201,7 +201,7 @@ typedef struct RumPageItemsStateData
201201
* On the {leaf, data} page, this is the number of
202202
* RumItem structures that are in the compressed posting list.
203203
*
204-
* On the {data} page, this is the number of PostingItem structures.
204+
* On the {data} page, this is the number of RumPostingItem structures.
205205
*
206206
* On the {leaf} page, this is the number of IndexTuple, each of
207207
* which contains a compressed posting list. In this case, the size
@@ -218,7 +218,7 @@ typedef struct RumPageItemsStateData
218218
* It is used where posting lists are scanned.
219219
* Sometimes only the RumItem it contains is used.
220220
*/
221-
PostingItem curPitem;
221+
RumPostingItem curPitem;
222222

223223
/* Current IndexTuple on the page */
224224
IndexTuple curItup;
@@ -638,8 +638,8 @@ get_entry_index_tuple_values(RumPageItemsState piState)
638638
if (piState->pageType == LEAF_ENTRY_PAGE &&
639639
RumGetAddInfoAttr(piState))
640640
{
641-
(piState)->curKeyAddInfoOid = RumGetAddInfoAttr(piState)->atttypid;
642-
(piState)->curKeyAddInfoByval = RumGetAddInfoAttr(piState)->attbyval;
641+
piState->curKeyAddInfoOid = RumGetAddInfoAttr(piState)->atttypid;
642+
piState->curKeyAddInfoByval = RumGetAddInfoAttr(piState)->attbyval;
643643
}
644644
}
645645

@@ -687,7 +687,7 @@ find_page_in_posting_tree(BlockNumber targetPageNum,
687687
{
688688
Page curPage;
689689
RumPageOpaque curOpaq;
690-
PostingItem curPitem;
690+
RumPostingItem curPitem;
691691
BlockNumber nextPageNum;
692692

693693
/* Page loop */
@@ -713,21 +713,21 @@ find_page_in_posting_tree(BlockNumber targetPageNum,
713713
}
714714

715715
/*
716-
* Reading the first PostingItem from the current page. This is
716+
* Reading the first RumPostingItem from the current page. This is
717717
* necessary to remember the link down.
718718
*/
719719
memcpy(&curPitem,
720-
RumDataPageGetItem(curPage, 1), sizeof(PostingItem));
721-
nextPageNum = PostingItemGetBlockNumber(&curPitem);
720+
RumDataPageGetItem(curPage, 1), sizeof(RumPostingItem));
721+
nextPageNum = RumPostingItemGetBlockNumber(&curPitem);
722722

723723
/* The loop that scans the page */
724724
for (int i = 1; i <= curOpaq->maxoff; i++)
725725
{
726-
/* Reading the PostingItem from the current page */
726+
/* Reading the RumPostingItem from the current page */
727727
memcpy(&curPitem,
728-
RumDataPageGetItem(curPage, i), sizeof(PostingItem));
728+
RumDataPageGetItem(curPage, i), sizeof(RumPostingItem));
729729

730-
if (targetPageNum == PostingItemGetBlockNumber(&curPitem))
730+
if (targetPageNum == RumPostingItemGetBlockNumber(&curPitem))
731731
{
732732
pfree(curPage);
733733
return true;

0 commit comments

Comments
 (0)