pgsql: Remove now-unnecessary cast.

Remove now-unnecessary cast. Etsuro Fujita Discussion: http://postgr.es/m/5ae99ba7.9060...@lab.ntt.co.jp Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/a365f52d58317e3b24e06564e1f6474ffa3221d4 Modified Files -- contrib/postgres_fdw/postgres_fdw.c | 2

pgsql: Improve our method for probing the availability of ARM CRC instr

Improve our method for probing the availability of ARM CRC instructions. Instead of depending on glibc's getauxval() function, just try to execute the CRC code, and trap SIGILL if that happens. Thomas Munro Discussion: https://postgr.es/m/he1pr0801mb1323d171938eabc04ffe7fa9e3...@he1pr0801mb1323

pgsql: Revert back-branch changes in power()'s behavior for NaN inputs.

Revert back-branch changes in power()'s behavior for NaN inputs. Per discussion, the value of fixing these bugs in the back branches doesn't outweigh the downsides of changing corner-case behavior in a minor release. Hence, revert commits 217d8f3a1 and 4d864de48 in the v10 branch and the correspo

pgsql: Revert back-branch changes in power()'s behavior for NaN inputs.

Revert back-branch changes in power()'s behavior for NaN inputs. Per discussion, the value of fixing these bugs in the back branches doesn't outweigh the downsides of changing corner-case behavior in a minor release. Hence, revert commits 217d8f3a1 and 4d864de48 in the v10 branch and the correspo

pgsql: Revert back-branch changes in power()'s behavior for NaN inputs.

Revert back-branch changes in power()'s behavior for NaN inputs. Per discussion, the value of fixing these bugs in the back branches doesn't outweigh the downsides of changing corner-case behavior in a minor release. Hence, revert commits 217d8f3a1 and 4d864de48 in the v10 branch and the correspo

pgsql: Revert back-branch changes in power()'s behavior for NaN inputs.

Revert back-branch changes in power()'s behavior for NaN inputs. Per discussion, the value of fixing these bugs in the back branches doesn't outweigh the downsides of changing corner-case behavior in a minor release. Hence, revert commits 217d8f3a1 and 4d864de48 in the v10 branch and the correspo

pgsql: Revert back-branch changes in power()'s behavior for NaN inputs.

Revert back-branch changes in power()'s behavior for NaN inputs. Per discussion, the value of fixing these bugs in the back branches doesn't outweigh the downsides of changing corner-case behavior in a minor release. Hence, revert commits 217d8f3a1 and 4d864de48 in the v10 branch and the correspo

pgsql: Prevent NaN in jsonb/plpython transform

Prevent NaN in jsonb/plpython transform As in e348e7ae5727a6da8678036d748e5c5af7deb6c9 for jsonb/plperl, prevent putting a NaN into a jsonb numeric field. Tests for this had been removed in 6278a2a262b63faaf47eb2371f6bcb5b6e3ff118, but in case they are ever resurrected: This would change the outp

pgsql: Suppress some compiler warnings in plperl on Windows.

Suppress some compiler warnings in plperl on Windows. Perl's XSUB.h header defines macros to replace libc functions. Our header port_win32.h does something similar earlier, so XSUB.h causes compiler warnings about macro redefinition. Undefine our macros before including XSUB.h. Thomas Munro Di

pgsql: Fix assorted compiler warnings seen in the buildfarm.

Fix assorted compiler warnings seen in the buildfarm. Failure to use DatumGetFoo/FooGetDatum macros correctly, or at all, causes some warnings about sign conversion. This is just cosmetic at the moment but in principle it's a type violation, so clean up the instances I could find. autoprewarm.c

pgsql: Fix bogus code for extracting extended-statistics data from sysc

Fix bogus code for extracting extended-statistics data from syscache. statext_dependencies_load and statext_ndistinct_load were not up to snuff, in addition to being randomly different from each other. In detail: * Deserialize the fetched bytea value before releasing the syscache entry, not afte

pgsql: Fix bogus code for extracting extended-statistics data from sysc

Fix bogus code for extracting extended-statistics data from syscache. statext_dependencies_load and statext_ndistinct_load were not up to snuff, in addition to being randomly different from each other. In detail: * Deserialize the fetched bytea value before releasing the syscache entry, not afte

pgsql: doc: Correct update on limitations of partitions

doc: Correct update on limitations of partitions Amit Langote Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/bcded2609ade6204badde506025b414c8e6ef0cd Modified Files -- doc/src/sgml/ddl.sgml | 7 +++ 1 file changed, 7 insertions(+)

pgsql: Remove remaining references to version-0 calling convention in d

Remove remaining references to version-0 calling convention in docs. Support for version-0 calling convention was removed in PostgreSQL v10. Change the SPI example to use version 1 convention, so that it actually works. Author: John Naylor Discussion: https://www.postgresql.org/message-id/cajvsv

pgsql: Remove remaining references to version-0 calling convention in d

Remove remaining references to version-0 calling convention in docs. Support for version-0 calling convention was removed in PostgreSQL v10. Change the SPI example to use version 1 convention, so that it actually works. Author: John Naylor Discussion: https://www.postgresql.org/message-id/cajvsv

pgsql: Fix some sloppiness in the new BufFileSize() and BufFileAppend()

Fix some sloppiness in the new BufFileSize() and BufFileAppend() functions. There were three related issues: * BufFileAppend() incorrectly reset the seek position on the 'source' file. As a result, if you had called BufFileRead() on the file before calling BufFileAppend(), it got confused, an

pgsql: docs: Remove tabs recently introduced by me.

docs: Remove tabs recently introduced by me. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/7f6570b3a8d1aa8e90ab0868eefa5a4236b0ada3 Modified Files -- doc/src/sgml/release.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)