mirror of
https://github.com/postgres/postgres.git
synced 2025-06-26 12:21:12 +03:00
Doc: improve documentation about width_bucket().
Specify whether the bucket bounds are inclusive or exclusive, and improve some other vague language. Explain the behavior that occurs when the "low" bound is greater than the "high" bound. Make width_bucket_numeric's comment more like that for width_bucket_float8, in particular noting that infinite bounds are rejected (since they became possible in v14). Reported-by: Ben Peachey Higdon <bpeacheyhigdon@gmail.com> Author: Robert Treat <rob@xzilla.net> Co-authored-by: Tom Lane <tgl@sss.pgh.pa.us> Reviewed-by: Dean Rasheed <dean.a.rasheed@gmail.com> Discussion: https://postgr.es/m/2BD74F86-5B89-4AC1-8F13-23CED3546AC1@gmail.com Backpatch-through: 13
This commit is contained in:
@ -4010,8 +4010,8 @@ float84ge(PG_FUNCTION_ARGS)
|
||||
* in the histogram. width_bucket() returns an integer indicating the
|
||||
* bucket number that 'operand' belongs to in an equiwidth histogram
|
||||
* with the specified characteristics. An operand smaller than the
|
||||
* lower bound is assigned to bucket 0. An operand greater than the
|
||||
* upper bound is assigned to an additional bucket (with number
|
||||
* lower bound is assigned to bucket 0. An operand greater than or equal
|
||||
* to the upper bound is assigned to an additional bucket (with number
|
||||
* count+1). We don't allow "NaN" for any of the float8 inputs, and we
|
||||
* don't allow either of the histogram bounds to be +/- infinity.
|
||||
*/
|
||||
|
Reference in New Issue
Block a user