pgsql: Repair double-free in SP-GIST rescan (bug #15378)

2018-09-11 Thread Andrew Gierth
Repair double-free in SP-GIST rescan (bug #15378) spgrescan would first reset traversalCxt, and then traverse a potentially non-empty stack containing pointers to traversalValues which had been allocated in those contexts, freeing them a second time. This bug originates in commit ccd6eb49a where t

pgsql: Repair double-free in SP-GIST rescan (bug #15378)

2018-09-11 Thread Andrew Gierth
Repair double-free in SP-GIST rescan (bug #15378) spgrescan would first reset traversalCxt, and then traverse a potentially non-empty stack containing pointers to traversalValues which had been allocated in those contexts, freeing them a second time. This bug originates in commit ccd6eb49a where t

pgsql: Repair double-free in SP-GIST rescan (bug #15378)

2018-09-11 Thread Andrew Gierth
Repair double-free in SP-GIST rescan (bug #15378) spgrescan would first reset traversalCxt, and then traverse a potentially non-empty stack containing pointers to traversalValues which had been allocated in those contexts, freeing them a second time. This bug originates in commit ccd6eb49a where t

pgsql: Repair double-free in SP-GIST rescan (bug #15378)

2018-09-11 Thread Andrew Gierth
Repair double-free in SP-GIST rescan (bug #15378) spgrescan would first reset traversalCxt, and then traverse a potentially non-empty stack containing pointers to traversalValues which had been allocated in those contexts, freeing them a second time. This bug originates in commit ccd6eb49a where t

pgsql: Support building with Visual Studio 2017

2018-09-11 Thread Andrew Dunstan
Support building with Visual Studio 2017 Haribabu Kommi, reviewed by Takeshi Ideriha and Christian Ullrich Now backpatched to 9.4 and 9.3 Branch -- REL9_4_STABLE Details --- https://git.postgresql.org/pg/commitdiff/19acfd6528bcbf55ad996397177a1f2a16001c25 Modified Files --

pgsql: Support building with Visual Studio 2017

2018-09-11 Thread Andrew Dunstan
Support building with Visual Studio 2017 Haribabu Kommi, reviewed by Takeshi Ideriha and Christian Ullrich Now backpatched to 9.4 and 9.3 Branch -- REL9_3_STABLE Details --- https://git.postgresql.org/pg/commitdiff/48c978f3ed20961a69189eab2e26e0fa0f54986f Modified Files --

pgsql: Support building with Visual Studio 2017

2018-09-11 Thread Andrew Dunstan
Support building with Visual Studio 2017 Haribabu Kommi, reviewed by Takeshi Ideriha and Christian Ullrich Backpatch to 9.6 Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/f6c268c4894bba9d1bbc5338407febaaad0dbd04 Modified Files -- doc/src/sgml/i

pgsql: Support building with Visual Studio 2015

2018-09-11 Thread Andrew Dunstan
Support building with Visual Studio 2015 Adjust the way we detect the locale. As a result the minumum Windows version supported by VS2015 and later is Windows Vista. Add some tweaks to remove new compiler warnings. Remove documentation references to the now obsolete msysGit. Michael Paquier, some

pgsql: Support building with Visual Studio 2015

2018-09-11 Thread Andrew Dunstan
Support building with Visual Studio 2015 Adjust the way we detect the locale. As a result the minumum Windows version supported by VS2015 and later is Windows Vista. Add some tweaks to remove new compiler warnings. Remove documentation references to the now obsolete msysGit. Michael Paquier, some

pgsql: Remove ruleutils.c's special case for BIT [VARYING] literals.

2018-09-11 Thread Tom Lane
Remove ruleutils.c's special case for BIT [VARYING] literals. Up to now, get_const_expr() insisted on prefixing BIT and VARBIT literals with 'B'. That's not really necessary, because we always append explicit-cast syntax to identify the constant's type. Moreover, it's subtly wrong for VARBIT, bec

pgsql: Remove ruleutils.c's special case for BIT [VARYING] literals.

2018-09-11 Thread Tom Lane
Remove ruleutils.c's special case for BIT [VARYING] literals. Up to now, get_const_expr() insisted on prefixing BIT and VARBIT literals with 'B'. That's not really necessary, because we always append explicit-cast syntax to identify the constant's type. Moreover, it's subtly wrong for VARBIT, bec

pgsql: doc: adjust PG 11 release notes

2018-09-11 Thread Bruce Momjian
doc: adjust PG 11 release notes Fixes for channel binding, SQL procedures, and pg_trgm. Backpatch-through: 11 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/0d45cd96fd0f3387d1bcf7e6f873c73c4f251df8 Modified Files -- doc/src/sgml/release-11.sgml | 15

pgsql: doc: adjust PG 11 release notes

2018-09-11 Thread Bruce Momjian
doc: adjust PG 11 release notes Fixes for channel binding, SQL procedures, and pg_trgm. Backpatch-through: 11 Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/293010a68afd5b3a1f1e7621d5c89ba422c21d09 Modified Files -- doc/src/sgml/release-11.sgm

pgsql: Parse more strictly integer parameters from connection strings i

2018-09-11 Thread Michael Paquier
Parse more strictly integer parameters from connection strings in libpq The following parameters have been parsed in lossy ways when specified in a connection string processed by libpq: - connect_timeout - keepalives - keepalives_count - keepalives_idle - keepalives_interval - port Overflowing va

pgsql: Add PQresultMemorySize function to report allocated size of a PG

2018-09-11 Thread Tom Lane
Add PQresultMemorySize function to report allocated size of a PGresult. This number can be useful for application memory management, and the overhead to track it seems pretty trivial. Lars Kanis, reviewed by Pavel Stehule, some mods by me Discussion: https://postgr.es/m/fa16a288-9685-14f2-97c8-