aboutsummaryrefslogtreecommitdiff
path: root/src/include/executor/nodeModifyTable.h
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-04-04 11:28:33 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2018-04-04 11:28:40 -0400
commit331b2369c0ad1e51d5e50bf5dd75232e0160553a (patch)
treec4664e95d32549da837b34db0b1305773618c7c9 /src/include/executor/nodeModifyTable.h
parent3a5e0a91bb324ad2b2b1a0623a3f2e37772b43fc (diff)
downloadpostgresql-331b2369c0ad1e51d5e50bf5dd75232e0160553a.tar.gz
postgresql-331b2369c0ad1e51d5e50bf5dd75232e0160553a.zip
Fix platform and Perl-version dependencies in new jsonb_plperl code.
Testing SvTYPE() directly is more fraught with problems than one might think, because depending on context Perl might be storing a scalar value in one of several forms, eg both numeric and string values. This resulted in Perl-version-dependent buildfarm test failures. Instead use the SvTYPE test only to distinguish non-scalar cases (AV, HV, NULL). Disambiguate scalars by testing SvIOK, SvNOK, then SvPOK. This creates a preference order for how we will resolve cases where the value is available in more than one form, which seems fine to me. Furthermore, because we're now dealing directly with a "double" value in the SvNOK case, we can get rid of an inadequate and unportable string-comparison test for infinities, and use isinf() instead. (We do need some additional #include and "-lm" infrastructure to use that in a contrib module, per prior experiences.) In passing, prevent the regression test results from depending on DROP CASCADE order; I've not seen that malfunction, but it's trouble waiting to happen. Discussion: https://postgr.es/m/E1f3MMJ-0006bf-B0@gemulon.postgresql.org
Diffstat (limited to 'src/include/executor/nodeModifyTable.h')
0 files changed, 0 insertions, 0 deletions