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

Commit9e945f8

Browse files
committed
Fix Latin spelling
"c.f." should be "cf.".
1 parentf50c80d commit9e945f8

File tree

8 files changed

+9
-9
lines changed

8 files changed

+9
-9
lines changed

‎src/backend/catalog/catalog.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ IsCatalogClass(Oid relid, Form_pg_class reltuple)
120120
* this is noticeably cheaper and doesn't require catalog access.
121121
*
122122
* This test is safe since even an oid wraparound will preserve this
123-
* property (c.f. GetNewObjectId()) and it has the advantage that it works
123+
* property (cf. GetNewObjectId()) and it has the advantage that it works
124124
* correctly even if a user decides to create a relation in the pg_catalog
125125
* namespace.
126126
* ----

‎src/backend/optimizer/util/clauses.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1611,7 +1611,7 @@ contain_leaked_vars_walker(Node *node, void *context)
16111611
* WHERE CURRENT OF doesn't contain leaky function calls.
16121612
* Moreover, it is essential that this is considered non-leaky,
16131613
* since the planner must always generate a TID scan when CURRENT
1614-
* OF is present --c.f. cost_tidscan.
1614+
* OF is present --cf. cost_tidscan.
16151615
*/
16161616
return false;
16171617

‎src/backend/replication/logical/origin.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@
6060
* all our platforms, but it also simplifies memory ordering concerns
6161
* between the remote and local lsn. We use a lwlock instead of a spinlock
6262
* so it's less harmful to hold the lock over a WAL write
63-
* (c.f. AdvanceReplicationProgress).
63+
* (cf. AdvanceReplicationProgress).
6464
*
6565
* ---------------------------------------------------------------------------
6666
*/

‎src/backend/replication/logical/reorderbuffer.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@
1515
* they are written to the WAL and is responsible to reassemble them into
1616
* toplevel transaction sized pieces. When a transaction is completely
1717
* reassembled - signalled by reading the transaction commit record - it
18-
* will then call the output plugin (c.f. ReorderBufferCommit()) with the
18+
* will then call the output plugin (cf. ReorderBufferCommit()) with the
1919
* individual changes. The output plugins rely on snapshots built by
2020
* snapbuild.c which hands them to us.
2121
*
@@ -1752,7 +1752,7 @@ ReorderBufferForget(ReorderBuffer *rb, TransactionId xid, XLogRecPtr lsn)
17521752
/*
17531753
* Execute invalidations happening outside the context of a decoded
17541754
* transaction. That currently happens either for xid-less commits
1755-
* (c.f. RecordTransactionCommit()) or for invalidations in uninteresting
1755+
* (cf. RecordTransactionCommit()) or for invalidations in uninteresting
17561756
* transactions (via ReorderBufferForget()).
17571757
*/
17581758
void

‎src/backend/replication/logical/snapbuild.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@
4242
* catalog in a transaction. During normal operation this is achieved by using
4343
* CommandIds/cmin/cmax. The problem with that however is that for space
4444
* efficiency reasons only one value of that is stored
45-
* (c.f. combocid.c). Since ComboCids are only available in memory we log
45+
* (cf. combocid.c). Since ComboCids are only available in memory we log
4646
* additional information which allows us to get the original (cmin, cmax)
4747
* pair during visibility checks. Check the reorderbuffer.c's comment above
4848
* ResolveCminCmaxDuringDecoding() for details.

‎src/backend/storage/ipc/procarray.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -820,7 +820,7 @@ ProcArrayApplyRecoveryInfo(RunningTransactions running)
820820

821821
/*
822822
* latestObservedXid is at least set to the point where SUBTRANS was
823-
* started up to (c.f. ProcArrayInitRecovery()) or to the biggest xid
823+
* started up to (cf. ProcArrayInitRecovery()) or to the biggest xid
824824
* RecordKnownAssignedTransactionIds() was called for. Initialize
825825
* subtrans from thereon, up to nextXid - 1.
826826
*

‎src/backend/utils/cache/relcache.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2511,7 +2511,7 @@ RelationClearRelation(Relation relation, bool rebuild)
25112511

25122512
/*
25132513
* This shouldn't happen as dropping a relation is intended to be
2514-
* impossible if still referenced (c.f. CheckTableNotInUse()). But
2514+
* impossible if still referenced (cf. CheckTableNotInUse()). But
25152515
* if we get here anyway, we can't just delete the relcache entry,
25162516
* as it possibly could get accessed later (as e.g. the error
25172517
* might get trapped and handled via a subtransaction rollback).

‎src/bin/psql/describe.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1722,7 +1722,7 @@ describeOneTableDetails(const char *schemaname,
17221722

17231723
/*
17241724
* In 9.0+, we have column comments for: relations, views, composite
1725-
* types, and foreign tables (c.f. CommentObject() in comment.c).
1725+
* types, and foreign tables (cf. CommentObject() in comment.c).
17261726
*/
17271727
if (tableinfo.relkind==RELKIND_RELATION||
17281728
tableinfo.relkind==RELKIND_VIEW||

0 commit comments

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