]> granicus.if.org Git - postgresql/commit
Document security implications of qualified names.
authorNoah Misch <noah@leadboat.com>
Sun, 29 Jul 2018 03:08:01 +0000 (20:08 -0700)
committerNoah Misch <noah@leadboat.com>
Sun, 29 Jul 2018 03:08:08 +0000 (20:08 -0700)
commita117c7a7b62f8978052b69e8e3bfdf8f8099a61d
tree6ea3a14339761f58ab221217c6e2046177f355e3
parent9a513f8f9e87462ec63a9f08bcd2d4a7e1f6fa4d
Document security implications of qualified names.

Commit 5770172cb0c9df9e6ce27c507b449557e5b45124 documented secure schema
usage, and that advice suffices for using unqualified names securely.
Document, in typeconv-func primarily, the additional issues that arise
with qualified names.  Back-patch to 9.3 (all supported versions).

Reviewed by Jonathan S. Katz.

Discussion: https://postgr.es/m/20180721012446.GA1840594@rfd.leadboat.com
doc/src/sgml/ddl.sgml
doc/src/sgml/ref/create_function.sgml
doc/src/sgml/syntax.sgml
doc/src/sgml/typeconv.sgml
doc/src/sgml/xfunc.sgml
src/backend/utils/adt/ruleutils.c