Commit0510b62

committed

Typo fixes.

All noted by Jaime Casanova.

1 parent99b60fc commit0510b62Copy full SHA for 0510b62

File tree

-3

lines changed

-3

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -104,7 +104,7 @@ CREATE [ OR REPLACE ] [ TEMP \| TEMPORARY ] VIEW <replaceable class="PARAMETER">n`
`104`	`104`	`<listitem>`
`105`	`105`	`<para>`
`106`	`106`	`This clause specifies optional parameters for a view; currently, the`
`107`		`- onlysuppored parameter name is <literal>security_barrier</literal>,`
	`107`	`+ onlysupported parameter name is <literal>security_barrier</literal>,`
`108`	`108`	`which should be enabled when a view is intended to provide row-level`
`109`	`109`	`security. See <xref linkend="rules-privileges"> for full details.`
`110`	`110`	`</para>`

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -1876,7 +1876,7 @@ SELECT * FROM phone_number WHERE tricky(person, phone);`
`1876`	`1876`	`When it is necessary for a view to provide row-level security, the`
`1877`	`1877`	`<literal>security_barrier</literal> attribute should be applied to`
`1878`	`1878`	`the view. This prevents maliciously-chosen functions and operators from`
`1879`		`- being invoked on rows untilafterthe view has done its work. For`
	`1879`	`+ being invoked on rows untilafter the view has done its work. For`
`1880`	`1880`	`example, if the view shown above had been created like this, it would`
`1881`	`1881`	`be secure:`
`1882`	`1882`	`<programlisting>`
`@@ -1893,7 +1893,7 @@ CREATE VIEW phone_number WITH (security_barrier) AS`
`1893`	`1893`	`<para>`
`1894`	`1894`	`It is important to understand that even a view created with the`
`1895`	`1895`	`<literal>security_barrier</literal> option is intended to be secure only`
`1896`		`- in the limited sense that the contents of the invisible tuples will not`
	`1896`	`+ in the limited sense that the contents of the invisible tuples will not be`
`1897`	`1897`	`passed to possibly-insecure functions. The user may well have other means`
`1898`	`1898`	`of making inferences about the unseen data; for example, they can see the`
`1899`	`1899`	`query plan using <command>EXPLAIN</command>, or measure the runtime of`

Comments

(0)