Document changes in large-object privilege checking.
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 14 Nov 2017 17:33:10 +0000 (12:33 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 14 Nov 2017 17:33:10 +0000 (12:33 -0500)
commit6d776522d243d38faca6924d9b3c7cfaf0c4860d
tree438609f77164d191fea3011e9a0301fc489f348d
parenta61f5ab986386628cf20b33971364475ce452412
Document changes in large-object privilege checking.

Commit 5ecc0d738 removed the hard-wired superuser checks in lo_import
and lo_export in favor of protecting them with SQL permissions, but
failed to adjust the documentation to match.  Fix that, and add a
<caution> paragraph pointing out the nontrivial security hazards
involved with actually granting such permissions.  (It's still better
than ALLOW_DANGEROUS_LO_FUNCTIONS, though.)

Also, commit ae20b23a9 caused large object read/write privilege to
be checked during lo_open() rather than in the actual read or write
calls.  Document that.

Discussion: https://postgr.es/m/CAB7nPqRHmNOYbETnc_2EjsuzSM00Z+BWKv9sy6tnvSd5gWT_JA@mail.gmail.com
doc/src/sgml/config.sgml
doc/src/sgml/lobj.sgml