NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit530bcf7

committed

Fix thinko in comment

The listed numbers disagreed with the ones being used in the symbols;but instead of just fixing the numbers in the comment, use the symbolicname instead, which seems clearer.This has been wrong all along, so apply back to 9.5 where BRIN wasintroduced.Reported-by: Tomas VondraDiscussion:https://postgr.es/m/5ff514f2-8b1e-6366-b11c-8e2ed442562d@2ndquadrant.com

1 parent186b6df commit530bcf7Copy full SHA for 530bcf7

File tree

1 file changed

-4

lines changed

src/backend/access/brin
- brin_inclusion.c

1 file changed

-4

lines changed

`‎src/backend/access/brin/brin_inclusion.c`

Lines changed: 8 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -59,10 +59,14 @@`
`59`	`59`	`/*-`
`60`	`60`	`* The values stored in the bv_values arrays correspond to:`
`61`	`61`	`*`
`62`		`- * 0 - the union of the values in the block range`
`63`		`- * 1 - whether an empty value is present in any tuple in the block range`
`64`		`- * 2 - whether the values in the block range cannot be merged (e.g. an IPv6`
`65`		`- * address amidst IPv4 addresses).`
	`62`	`+ * INCLUSION_UNION`
	`63`	`+ *the union of the values in the block range`
	`64`	`+ * INCLUSION_UNMERGEABLE`
	`65`	`+ *whether the values in the block range cannot be merged`
	`66`	`+ *(e.g. an IPv6 address amidst IPv4 addresses)`
	`67`	`+ * INCLUSION_CONTAINS_EMPTY`
	`68`	`+ *whether an empty value is present in any tuple`
	`69`	`+ *in the block range`
`66`	`70`	`*/`
`67`	`71`	`#defineINCLUSION_UNION0`
`68`	`72`	`#defineINCLUSION_UNMERGEABLE1`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit530bcf7

File tree

1 file changed

1 file changed

`‎src/backend/access/brin/brin_inclusion.c`

0 commit comments