public inbox for [email protected]  
help / color / mirror / Atom feed
From: Erik Rijkers <[email protected]>
To: [email protected]
Subject: the the
Date: Mon, 4 May 2015 22:48:35 +0200
Message-ID: <[email protected]> (raw)
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>

typos: 2x the the

-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs


Attachments:

  [text/x-patch] func.sgml.diff (462B, 2-func.sgml.diff)
  download | inline diff:
--- doc/src/sgml/func.sgml.orig	2015-05-04 21:38:54.558334172 +0200
+++ doc/src/sgml/func.sgml	2015-05-04 21:39:17.238883916 +0200
@@ -17054,7 +17054,7 @@
         <parameter>internal_id</parameter> <type>oid</type>
        </entry>
        <entry>
-        Create a replication origin with the the passed in external
+        Create a replication origin with the passed in external
         name, and create an internal id for it.
        </entry>
       </row>

  [text/x-patch] origin.c.diff (727B, 3-origin.c.diff)
  download | inline diff:
--- src/backend/replication/logical/origin.c.orig	2015-05-04 21:39:30.063621404 +0200
+++ src/backend/replication/logical/origin.c	2015-05-04 21:39:42.861354091 +0200
@@ -798,7 +798,7 @@
  * that originated at the LSN remote_commit on the remote node was replayed
  * successfully and that we don't need to do so again. In combination with
  * setting up replorigin_sesssion_origin_lsn and replorigin_sesssion_origin that ensures we
- * won't loose knowledge about that after a crash if the the transaction had a
+ * won't loose knowledge about that after a crash if the transaction had a
  * persistent effect (think of asynchronous commits).
  *
  * local_commit needs to be a local LSN of the commit so that we can make sure

view thread (2+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected]
  Subject: Re: the the
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox