Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit4cb560b

Browse files
committed
Consistently spell "leakproof" without a hyphen.
The overwhelming majority of places already did this, but a smallhandful of places had a hyphen.Yugo Nagata.Discussion:https://postgr.es/m/CAEZATCXnnuORE2BoGwHw2zbtVvsPOLhbfVmEk9GxRzK%2Bx3OW-Q%40mail.gmail.com
1 parent2355e51 commit4cb560b

File tree

6 files changed

+8
-8
lines changed

6 files changed

+8
-8
lines changed

‎doc/src/sgml/catalogs.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6040,7 +6040,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
60406040
The function has no side effects. No information about the
60416041
arguments is conveyed except via the return value. Any function
60426042
that might throw an error depending on the values of its arguments
6043-
is notleak-proof.
6043+
is notleakproof.
60446044
</para></entry>
60456045
</row>
60466046

‎doc/src/sgml/planstats.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -740,7 +740,7 @@ EXPLAIN (ANALYZE, TIMING OFF, BUFFERS OFF) SELECT * FROM t WHERE a &lt;= 49 AND
740740
error, in which case this mechanism is invisible in practice. But if the
741741
user is reading from a security-barrier view, then the planner might wish
742742
to check the statistics of an underlying table that is otherwise
743-
inaccessible to the user. In that case, the operator should beleak-proof
743+
inaccessible to the user. In that case, the operator should beleakproof
744744
or the statistics will not be used. There is no direct feedback about
745745
that, except that the plan might be suboptimal. If one suspects that this
746746
is the case, one could try running the query as a more privileged user,

‎doc/src/sgml/rules.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2162,7 +2162,7 @@ CREATE VIEW phone_number WITH (security_barrier) AS
21622162
<literal>LEAKPROOF</literal> to be pushed down, as they never receive data
21632163
from the view. In contrast, a function that might throw an error depending
21642164
on the values received as arguments (such as one that throws an error in the
2165-
event of overflow or division by zero) is notleak-proof, and could provide
2165+
event of overflow or division by zero) is notleakproof, and could provide
21662166
significant information about the unseen rows if applied before the security
21672167
view's row filters.
21682168
</para>

‎src/backend/statistics/extended_stats.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1397,7 +1397,7 @@ statext_is_compatible_clause_internal(PlannerInfo *root, Node *clause,
13971397
/*
13981398
* If there are any securityQuals on the RTE from security barrier
13991399
* views or RLS policies, then the user may not have access to all the
1400-
* table's data, and we must check that the operator isleak-proof.
1400+
* table's data, and we must check that the operator isleakproof.
14011401
*
14021402
* If the operator is leaky, then we must ignore this clause for the
14031403
* purposes of estimating with MCV lists, otherwise the operator might
@@ -1464,7 +1464,7 @@ statext_is_compatible_clause_internal(PlannerInfo *root, Node *clause,
14641464
/*
14651465
* If there are any securityQuals on the RTE from security barrier
14661466
* views or RLS policies, then the user may not have access to all the
1467-
* table's data, and we must check that the operator isleak-proof.
1467+
* table's data, and we must check that the operator isleakproof.
14681468
*
14691469
* If the operator is leaky, then we must ignore this clause for the
14701470
* purposes of estimating with MCV lists, otherwise the operator might

‎src/backend/utils/adt/selfuncs.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5763,7 +5763,7 @@ examine_simple_variable(PlannerInfo *root, Var *var,
57635763
* Check whether it is permitted to call func_oid passing some of the
57645764
* pg_statistic data in vardata. We allow this either if the user has SELECT
57655765
* privileges on the table or column underlying the pg_statistic data or if
5766-
* the function is markedleak-proof.
5766+
* the function is markedleakproof.
57675767
*/
57685768
bool
57695769
statistic_proc_security_check(VariableStatData*vardata,Oidfunc_oid)
@@ -5778,7 +5778,7 @@ statistic_proc_security_check(VariableStatData *vardata, Oid func_oid)
57785778
return true;
57795779

57805780
ereport(DEBUG2,
5781-
(errmsg_internal("not using statistics because function \"%s\" is notleak-proof",
5781+
(errmsg_internal("not using statistics because function \"%s\" is notleakproof",
57825782
get_func_name(func_oid))));
57835783
return false;
57845784
}

‎src/include/catalog/pg_proc.h

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ CATALOG(pg_proc,1255,ProcedureRelationId) BKI_BOOTSTRAP BKI_ROWTYPE_OID(81,Proce
6161
/* security definer */
6262
boolprosecdefBKI_DEFAULT(f);
6363

64-
/* is it aleak-proof function? */
64+
/* is it aleakproof function? */
6565
boolproleakproofBKI_DEFAULT(f);
6666

6767
/* strict with respect to NULLs? */

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp