database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-26 12:21:12 +03:00
Code Activity

Clarify some comments making use of leetspeak term "up2date"

Browse Source 
Most of these are new, as of a8fd13c, and "up-to-date" is much easier to
parse for the average reader.

Author: Peter Smith
Discussion: https://postgr.es/m/CAHut+PtHbHvgOjs_R9LyDF21j-Wn8SxoTtWMQNP2ifXN6t2cSg@mail.gmail.com
This commit is contained in:
Michael Paquier
2021-07-28 10:31:24 +09:00
parent b0483263dd
commit 7b7fbe1e8b
2 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/backend/jit/llvm/llvmjit_expr.c
View File

@ -2386,7 +2386,7 @@ llvm_compile_expr(ExprState *state)
* Run compiled expression.
*
* This will only be called the first time a JITed expression is called. We
* first make sure the expression is still up2date, and then get a pointer to
* first make sure the expression is still up-to-date, and then get a pointer to
* the emitted function. The latter can be the first thing that triggers
* optimizing and emitting all the generated functions.
*/

24
src/backend/replication/logical/logical.c
View File

@ -1048,7 +1048,7 @@ change_cb_wrapper(ReorderBuffer *cache, ReorderBufferTXN *txn,
ctx->write_xid = txn->xid;
/*
* report this change's lsn so replies from clients can give an up2date
* Report this change's lsn so replies from clients can give an up-to-date
* answer. This won't ever be enough (and shouldn't be!) to confirm
* receipt of this transaction, but it might allow another transaction's
* commit to be confirmed with one message.
@ -1088,7 +1088,7 @@ truncate_cb_wrapper(ReorderBuffer *cache, ReorderBufferTXN *txn,
ctx->write_xid = txn->xid;
/*
* report this change's lsn so replies from clients can give an up2date
* Report this change's lsn so replies from clients can give an up-to-date
* answer. This won't ever be enough (and shouldn't be!) to confirm
* receipt of this transaction, but it might allow another transaction's
* commit to be confirmed with one message.
@ -1225,10 +1225,10 @@ stream_start_cb_wrapper(ReorderBuffer *cache, ReorderBufferTXN *txn,
ctx->write_xid = txn->xid;
/*
* report this message's lsn so replies from clients can give an up2date
* answer. This won't ever be enough (and shouldn't be!) to confirm
* receipt of this transaction, but it might allow another transaction's
* commit to be confirmed with one message.
* Report this message's lsn so replies from clients can give an
* up-to-date answer. This won't ever be enough (and shouldn't be!) to
* confirm receipt of this transaction, but it might allow another
* transaction's commit to be confirmed with one message.
*/
ctx->write_location = first_lsn;
@ -1272,10 +1272,10 @@ stream_stop_cb_wrapper(ReorderBuffer *cache, ReorderBufferTXN *txn,
ctx->write_xid = txn->xid;
/*
* report this message's lsn so replies from clients can give an up2date
* answer. This won't ever be enough (and shouldn't be!) to confirm
* receipt of this transaction, but it might allow another transaction's
* commit to be confirmed with one message.
* Report this message's lsn so replies from clients can give an
* up-to-date answer. This won't ever be enough (and shouldn't be!) to
* confirm receipt of this transaction, but it might allow another
* transaction's commit to be confirmed with one message.
*/
ctx->write_location = last_lsn;
@ -1443,7 +1443,7 @@ stream_change_cb_wrapper(ReorderBuffer *cache, ReorderBufferTXN *txn,
ctx->write_xid = txn->xid;
/*
* report this change's lsn so replies from clients can give an up2date
* Report this change's lsn so replies from clients can give an up-to-date
* answer. This won't ever be enough (and shouldn't be!) to confirm
* receipt of this transaction, but it might allow another transaction's
* commit to be confirmed with one message.
@ -1535,7 +1535,7 @@ stream_truncate_cb_wrapper(ReorderBuffer *cache, ReorderBufferTXN *txn,
ctx->write_xid = txn->xid;
/*
* report this change's lsn so replies from clients can give an up2date
* Report this change's lsn so replies from clients can give an up-to-date
* answer. This won't ever be enough (and shouldn't be!) to confirm
* receipt of this transaction, but it might allow another transaction's
* commit to be confirmed with one message.