]> git.ipfire.org Git - thirdparty/postgresql.git/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:34 +0000 (20:08 -0700)
commit8c477a42eb9bdb91e7361645c3c343578000cb4a
treefbf3d18155f87755dd3891f5be5cedacd0a1a49b
parentf878781066f64a82238423cc81cdf1f8f75a013d
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