aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2012-03-15 16:49:44 -0400
committerRobert Haas <rhaas@postgresql.org>2012-03-15 16:49:44 -0400
commit4012810a688f37ea12159f93d3ab0a1ed47ca3dc (patch)
tree38b6a0ad28e3c7e89ec0b211f6e4c9c96fe45a58 /doc/src
parentd0ed9efdf713f1bd8cdb5897d3f0c825986ff3b4 (diff)
downloadpostgresql-4012810a688f37ea12159f93d3ab0a1ed47ca3dc.tar.gz
postgresql-4012810a688f37ea12159f93d3ab0a1ed47ca3dc.zip
A couple more fixes for the sepgsql documentation.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/sepgsql.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/sepgsql.sgml b/doc/src/sgml/sepgsql.sgml
index ce752f3dbeb..07c6b99f45e 100644
--- a/doc/src/sgml/sepgsql.sgml
+++ b/doc/src/sgml/sepgsql.sgml
@@ -561,8 +561,8 @@ ERROR: SELinux: security policy violation
</para>
<para>
A combination of dynamic domain transition and trusted procedure
- enables an interesting use case that fits the typical process life-
- cycle of connection pooling software.
+ enables an interesting use case that fits the typical process life-cycle
+ of connection pooling software.
Even if your connection pooling software is not allowed to run most
of SQL commands, you can allow it to switch the security label
of the client using the <literal>sepgsql_setcon()</literal> function
@@ -576,7 +576,7 @@ ERROR: SELinux: security policy violation
procedure with appropriate permissions checks.
The point here is that only the trusted procedure actually has permission
to change the effective security label, and only does so when given proper
- credentials. Of course, for secure operation, the credential store must
+ credentials. Of course, for secure operation, the credential store
(table, procedure definition, or whatever) must be protected from
unauthorized access.
</para>