Fix PQencryptPasswordConn to work with older server versions.
password_encryption was a boolean before version 10, so cope with "on" and
"off".
Also, change the behavior with "plain", to treat it the same as "md5".
We're discussing removing the password_encryption='plain' option from the
server
Credit Claudio as main author of feature
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/c22b59edd26fb69661188b040ea3e8776a533685
Modified Files
--
doc/src/sgml/release-10.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via
doc: PG 10 release note updates for psql, GiST, and markup
Reported-by: Andrew Borodin, Fabien COELHO, Dagfinn Ilmari Mannsaker
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/4f45beba7aea007cbae68eaea5d04d4cab7e4f62
Modified Files
--
Fix pfree-of-already-freed-tuple when rescanning a GiST index-only scan.
GiST's getNextNearest() function attempts to pfree the previously-returned
tuple if any (that is, scan->xs_hitup in HEAD, or scan->xs_itup in older
branches). However, if we are rescanning a plan node after ending a
Fix pfree-of-already-freed-tuple when rescanning a GiST index-only scan.
GiST's getNextNearest() function attempts to pfree the previously-returned
tuple if any (that is, scan->xs_hitup in HEAD, or scan->xs_itup in older
branches). However, if we are rescanning a plan node after ending a
Fix pfree-of-already-freed-tuple when rescanning a GiST index-only scan.
GiST's getNextNearest() function attempts to pfree the previously-returned
tuple if any (that is, scan->xs_hitup in HEAD, or scan->xs_itup in older
branches). However, if we are rescanning a plan node after ending a
doc: update PG 10 release notes
Mention vacuum verbose includes oldest xmin, BRIN index usage
estimation, and multi-column statistics.
Reported-by: Masahiko Sawada, Alvaro Herrera
Branch
--
master
Details
---
Change the way pg_dump retrieves partitioning info
This gets rid of the code that issued separate queries to retrieve the
partitioning parent-child relationship, parent partition key, and child
partition bound information. With this patch, the information is
retrieved instead using the queries
Fix cursor_to_xml in tableforest false mode
It only produced elements but no wrapping element.
By contrast, cursor_to_xmlschema produced a schema that is now correct
but did not previously match the XML data produced by cursor_to_xml.
In passing, also fix a minor misunderstanding about moving
Fix cursor_to_xml in tableforest false mode
It only produced elements but no wrapping element.
By contrast, cursor_to_xmlschema produced a schema that is now correct
but did not previously match the XML data produced by cursor_to_xml.
In passing, also fix a minor misunderstanding about moving
Fix cursor_to_xml in tableforest false mode
It only produced elements but no wrapping element.
By contrast, cursor_to_xmlschema produced a schema that is now correct
but did not previously match the XML data produced by cursor_to_xml.
In passing, also fix a minor misunderstanding about moving
Fix cursor_to_xml in tableforest false mode
It only produced elements but no wrapping element.
By contrast, cursor_to_xmlschema produced a schema that is now correct
but did not previously match the XML data produced by cursor_to_xml.
In passing, also fix a minor misunderstanding about moving
Fix cursor_to_xml in tableforest false mode
It only produced elements but no wrapping element.
By contrast, cursor_to_xmlschema produced a schema that is now correct
but did not previously match the XML data produced by cursor_to_xml.
In passing, also fix a minor misunderstanding about moving
13 matches
Mail list logo
