diff options
| author | Alexander Korotkov <akorotkov@postgresql.org> | 2020-07-11 03:21:00 +0300 |
|---|---|---|
| committer | Alexander Korotkov <akorotkov@postgresql.org> | 2020-07-11 03:21:57 +0300 |
| commit | f4ae676e3178124c2bc2b3a3530efe8f3cdbc442 (patch) | |
| tree | 1ed49c6a229e21e8535417a8ffdb5af150f03900 /src/tutorial/funcs.source | |
| parent | 3ec5f6b53dfb6acfe66a952edef1b6887da91777 (diff) | |
| download | postgresql-f4ae676e3178124c2bc2b3a3530efe8f3cdbc442.tar.gz postgresql-f4ae676e3178124c2bc2b3a3530efe8f3cdbc442.zip | |
Forbid numeric NaN in jsonpath
SQL standard doesn't define numeric Inf or NaN values. It appears even more
ridiculous to support then in jsonpath assuming JSON doesn't support these
values as well. This commit forbids returning NaN from .double(), which was
previously allowed. NaN can't be result of inner-jsonpath computation over
non-NaNs. So, we can not expect NaN in the jsonpath output.
Reported-by: Tom Lane
Discussion: https://postgr.es/m/203949.1591879542%40sss.pgh.pa.us
Author: Alexander Korotkov
Reviewed-by: Tom Lane
Backpatch-through: 12
Diffstat (limited to 'src/tutorial/funcs.source')
0 files changed, 0 insertions, 0 deletions