diff options
| author | Andres Freund <andres@anarazel.de> | 2017-03-14 17:04:36 -0700 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2017-03-14 17:04:36 -0700 |
| commit | 61d0c320b55902d321e69de2ec4e9a355959ea2c (patch) | |
| tree | 0a1f0be7e8d402a629230472f9eaf87836fd61cd /src | |
| parent | c44c47a773bd9073012935a29b0264d95920412c (diff) | |
| download | postgresql-61d0c320b55902d321e69de2ec4e9a355959ea2c.tar.gz postgresql-61d0c320b55902d321e69de2ec4e9a355959ea2c.zip | |
Improve grammar / fix typos in snapbuild.c.
Author: Erik Rijkers
Discussion: https://postgr.es/m/797c6c4496a1ae49cc69e90aa768bac2@xs4all.nl
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/replication/logical/snapbuild.c | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/src/backend/replication/logical/snapbuild.c b/src/backend/replication/logical/snapbuild.c index 52601a50c4f..e129a6b8e40 100644 --- a/src/backend/replication/logical/snapbuild.c +++ b/src/backend/replication/logical/snapbuild.c @@ -34,7 +34,7 @@ * xid. That is we keep a list of transactions between snapshot->(xmin, xmax) * that we consider committed, everything else is considered aborted/in * progress. That also allows us not to care about subtransactions before they - * have committed which means this modules, in contrast to HS, doesn't have to + * have committed which means this module, in contrast to HS, doesn't have to * care about suboverflowed subtransactions and similar. * * One complexity of doing this is that to e.g. handle mixed DDL/DML @@ -82,7 +82,7 @@ * Initially the machinery is in the START stage. When an xl_running_xacts * record is read that is sufficiently new (above the safe xmin horizon), * there's a state transition. If there were no running xacts when the - * runnign_xacts record was generated, we'll directly go into CONSISTENT + * running_xacts record was generated, we'll directly go into CONSISTENT * state, otherwise we'll switch to the FULL_SNAPSHOT state. Having a full * snapshot means that all transactions that start henceforth can be decoded * in their entirety, but transactions that started previously can't. In @@ -273,7 +273,7 @@ static bool SnapBuildRestore(SnapBuild *builder, XLogRecPtr lsn); /* * Allocate a new snapshot builder. * - * xmin_horizon is the xid >=which we can be sure no catalog rows have been + * xmin_horizon is the xid >= which we can be sure no catalog rows have been * removed, start_lsn is the LSN >= we want to replay commits. */ SnapBuild * @@ -1840,7 +1840,7 @@ CheckPointSnapBuild(void) char path[MAXPGPATH]; /* - * We start of with a minimum of the last redo pointer. No new replication + * We start off with a minimum of the last redo pointer. No new replication * slot will start before that, so that's a safe upper bound for removal. */ redo = GetRedoRecPtr(); @@ -1898,7 +1898,7 @@ CheckPointSnapBuild(void) /* * It's not particularly harmful, though strange, if we can't * remove the file here. Don't prevent the checkpoint from - * completing, that'd be cure worse than the disease. + * completing, that'd be a cure worse than the disease. */ if (unlink(path) < 0) { |