diff options
author | Michael Paquier <michael@paquier.xyz> | 2023-11-08 14:06:42 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2023-11-08 14:06:42 +0900 |
commit | 59fc39c0d5d9237b4912b40fd781f605df1fb4b0 (patch) | |
tree | 3ffe3f118412e6c8e6df2a23b20e2cd2c9915c6d /src/tutorial/funcs.c | |
parent | 33d5cf65f8c97d6bf085dffecb51c6a52d1f3f0d (diff) | |
download | postgresql-59fc39c0d5d9237b4912b40fd781f605df1fb4b0.tar.gz postgresql-59fc39c0d5d9237b4912b40fd781f605df1fb4b0.zip |
Enlarge assertion in bloom_init() for false_positive_rate
false_positive_rate is a parameter that can be set with the bloom
opclass in BRIN, and setting it to a value of exactly 0.25 would trigger
an assertion in the first INSERT done on the index with value set.
The assertion changed here relied on BLOOM_{MIN|MAX}_FALSE_POSITIVE_RATE
that are somewhat arbitrary values, and specifying an out-of-range value
would also trigger a failure when defining such an index. So, as-is,
the assertion was just doubling on the min-max check of the reloption.
This is now enlarged to check that it is a correct percentage value,
instead, based on a suggestion by Tom Lane.
Author: Alexander Lakhin
Reviewed-by: Tom Lane, Shihao Zhong
Discussion: https://postgr.es/m/17969-a6c54de48026d694@postgresql.org
Backpatch-through: 14
Diffstat (limited to 'src/tutorial/funcs.c')
0 files changed, 0 insertions, 0 deletions