database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-06 18:42:54 +03:00
Code Activity

Typo fixes.

Browse Source 
All noted by Jaime Casanova.
This commit is contained in:
Robert Haas
2011-12-22 17:57:17 -05:00
parent 99b60fc04e
commit 0510b62d91
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/ref/create_view.sgml
View File

@@ -104,7 +104,7 @@ CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] VIEW <replaceable class="PARAMETER">n
<listitem> <listitem>
<para> <para>
This clause specifies optional parameters for a view; currently, the This clause specifies optional parameters for a view; currently, the
only suppored parameter name is <literal>security_barrier</literal>, only supported parameter name is <literal>security_barrier</literal>,
which should be enabled when a view is intended to provide row-level which should be enabled when a view is intended to provide row-level
security. See <xref linkend="rules-privileges"> for full details. security. See <xref linkend="rules-privileges"> for full details.
</para> </para>

2
doc/src/sgml/rules.sgml
View File

@@ -1893,7 +1893,7 @@ CREATE VIEW phone_number WITH (security_barrier) AS
<para> <para>
It is important to understand that even a view created with the It is important to understand that even a view created with the
<literal>security_barrier</literal> option is intended to be secure only <literal>security_barrier</literal> option is intended to be secure only
in the limited sense that the contents of the invisible tuples will not in the limited sense that the contents of the invisible tuples will not be
passed to possibly-insecure functions. The user may well have other means passed to possibly-insecure functions. The user may well have other means
of making inferences about the unseen data; for example, they can see the of making inferences about the unseen data; for example, they can see the
query plan using <command>EXPLAIN</command>, or measure the runtime of query plan using <command>EXPLAIN</command>, or measure the runtime of