diff options
| author | Dean Rasheed <dean.a.rasheed@gmail.com> | 2025-01-14 13:50:54 +0000 |
|---|---|---|
| committer | Dean Rasheed <dean.a.rasheed@gmail.com> | 2025-01-14 13:50:54 +0000 |
| commit | 4cb560b53f8f9e9a94d593f9416c107ed8202110 (patch) | |
| tree | 8b45ef28a2a23f769b1f5487afdd8a77469fecc0 /doc/src | |
| parent | 2355e51110e7c687c125a5958f12a462931de996 (diff) | |
| download | postgresql-4cb560b53f8f9e9a94d593f9416c107ed8202110.tar.gz postgresql-4cb560b53f8f9e9a94d593f9416c107ed8202110.zip | |
Consistently spell "leakproof" without a hyphen.
The overwhelming majority of places already did this, but a small
handful of places had a hyphen.
Yugo Nagata.
Discussion: https://postgr.es/m/CAEZATCXnnuORE2BoGwHw2zbtVvsPOLhbfVmEk9GxRzK%2Bx3OW-Q%40mail.gmail.com
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/catalogs.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/planstats.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/rules.sgml | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 238ed679190..d3036c5ba9d 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -6040,7 +6040,7 @@ SCRAM-SHA-256$<replaceable><iteration count></replaceable>:<replaceable>&l The function has no side effects. No information about the arguments is conveyed except via the return value. Any function that might throw an error depending on the values of its arguments - is not leak-proof. + is not leakproof. </para></entry> </row> diff --git a/doc/src/sgml/planstats.sgml b/doc/src/sgml/planstats.sgml index 4fcfdc6e621..a909a5e3134 100644 --- a/doc/src/sgml/planstats.sgml +++ b/doc/src/sgml/planstats.sgml @@ -740,7 +740,7 @@ EXPLAIN (ANALYZE, TIMING OFF, BUFFERS OFF) SELECT * FROM t WHERE a <= 49 AND error, in which case this mechanism is invisible in practice. But if the user is reading from a security-barrier view, then the planner might wish to check the statistics of an underlying table that is otherwise - inaccessible to the user. In that case, the operator should be leak-proof + inaccessible to the user. In that case, the operator should be leakproof or the statistics will not be used. There is no direct feedback about that, except that the plan might be suboptimal. If one suspects that this is the case, one could try running the query as a more privileged user, diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml index 2b14db054de..7e98f5694b4 100644 --- a/doc/src/sgml/rules.sgml +++ b/doc/src/sgml/rules.sgml @@ -2162,7 +2162,7 @@ CREATE VIEW phone_number WITH (security_barrier) AS <literal>LEAKPROOF</literal> to be pushed down, as they never receive data from the view. In contrast, a function that might throw an error depending on the values received as arguments (such as one that throws an error in the - event of overflow or division by zero) is not leak-proof, and could provide + event of overflow or division by zero) is not leakproof, and could provide significant information about the unseen rows if applied before the security view's row filters. </para> |