pg-gin-strange-initialization.diff

text/x-patch

Filename: pg-gin-strange-initialization.diff

Type: text/x-patch

Part: 0

Message: BlockNumber initialized to InvalidBuffer?

Patch

Same data as JSON: GET /api/v1/attachments/:id/patch the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes. API reference →

Format: context

File	+	−
src/backend/access/gin/ginbtree.c	1	1

# InvalidBlockNumber is -1 (or rather 0xFFFFFFFF), while
# the currently used InvalidBuffer is 0, which is a valid
# BlockNumber.
============================================================
*** src/backend/access/gin/ginbtree.c	2d3e63387737b4034fc25ca3cb128d9ac57f4f01
--- src/backend/access/gin/ginbtree.c	67351e1b6541b25ab3c8e8dc7a57487c2422e124
*************** ginInsertValue(GinBtree btree, GinBtreeS
*** 276,282 ****
  ginInsertValue(GinBtree btree, GinBtreeStack *stack, GinStatsData *buildStats)
  {
  	GinBtreeStack *parent = stack;
! 	BlockNumber rootBlkno = InvalidBuffer;
  	Page		page,
  				rpage,
  				lpage;
--- 276,282 ----
  ginInsertValue(GinBtree btree, GinBtreeStack *stack, GinStatsData *buildStats)
  {
  	GinBtreeStack *parent = stack;
! 	BlockNumber rootBlkno = InvalidBlockNumber;
  	Page		page,
  				rpage,
  				lpage;