Four files with comment typos.
--- src/backend/replication/logical/decode.c.orig 2014-03-05 18:44:31.725317514 +0100
+++ src/backend/replication/logical/decode.c 2014-03-05 18:45:09.577190828 +0100
@@ -497,7 +497,7 @@
/* ----
* Check whether we are interested in this specific transaction, and tell
- * the the reorderbuffer to forget the content of the (sub-)transactions
+ * the reorderbuffer to forget the content of the (sub-)transactions
* if not.
*
* There basically two reasons we might not be interested in this
--- src/backend/replication/logical/logical.c.orig 2014-03-05 18:44:46.188875504 +0100
+++ src/backend/replication/logical/logical.c 2014-03-05 18:45:49.321041107 +0100
@@ -179,7 +179,7 @@
* perform the use-case dependent, actual, work.
*
* Needs to be called while in a memory context that's at least as long lived
- * as the the decoding context because further memory contexts will be created
+ * as the decoding context because further memory contexts will be created
* inside it.
*
* Returns an initialized decoding context after calling the output plugin's
@@ -334,7 +334,7 @@
* perform the use-case dependent, actual, work.
*
* Needs to be called while in a memory context that's at least as long lived
- * as the the decoding context because further memory contexts will be created
+ * as the decoding context because further memory contexts will be created
* inside it.
*
* Returns an initialized decoding context after calling the output plugin's
--- src/backend/replication/logical/reorderbuffer.c.orig 2014-03-05 18:46:16.515250612 +0100
+++ src/backend/replication/logical/reorderbuffer.c 2014-03-05 18:46:31.943799569 +0100
@@ -2741,7 +2741,7 @@
* * A tuple with a cmin but no cmax (and thus no combocid) got
* deleted/updated in another transaction than the one which created it
* which we are looking at right now. As only one of cmin, cmax or combocid
- * is actually stored in the heap we don't have access to the the value we
+ * is actually stored in the heap we don't have access to the value we
* need anymore.
*
* To resolve those problems we have a per-transaction hash of (cmin,
--- src/backend/storage/ipc/procarray.c.orig 2014-03-05 18:46:43.473461974 +0100
+++ src/backend/storage/ipc/procarray.c 2014-03-05 18:46:55.592106219 +0100
@@ -1948,7 +1948,7 @@
/*
* Acquire XidGenLock, so no transactions can acquire an xid while we're
* running. If no transaction with xid were running concurrently a new xid
- * could influence the the RecentXmin et al.
+ * could influence the RecentXmin et al.
*
* We initialize the computation to nextXid since that's guaranteed to be
* a safe, albeit pessimal, value.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
