database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-11 05:41:32 +03:00
Code

Fix thinko in comment

Browse Source 
The listed numbers disagreed with the ones being used in the symbols;
but instead of just fixing the numbers in the comment, use the symbolic
name instead, which seems clearer.

This has been wrong all along, so apply back to 9.5 where BRIN was
introduced.

Reported-by: Tomas Vondra
Discussion: https://postgr.es/m/5ff514f2-8b1e-6366-b11c-8e2ed442562d@2ndquadrant.com
This commit is contained in:
Alvaro Herrera 2018-03-26 12:00:25 -03:00
parent 356f85f95c
commit 43cd7abdcc
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/backend/access/brin/brin_inclusion.c
View File

@ -58,10 +58,14 @@
/*-
* The values stored in the bv_values arrays correspond to:
*
* 0 - the union of the values in the block range
* 1 - whether an empty value is present in any tuple in the block range
* 2 - whether the values in the block range cannot be merged (e.g. an IPv6
* address amidst IPv4 addresses).
* INCLUSION_UNION
* the union of the values in the block range
* INCLUSION_UNMERGEABLE
* whether the values in the block range cannot be merged
* (e.g. an IPv6 address amidst IPv4 addresses)
* INCLUSION_CONTAINS_EMPTY
* whether an empty value is present in any tuple
* in the block range
*/
#define INCLUSION_UNION 0
#define INCLUSION_UNMERGEABLE 1