Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M247190=pgsql-hackers-arkari@postgresql.org>)
 id 1WRyYp-0004lD-FG
 for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Mar 2014 06:40:39 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M247190=pgsql-hackers-arkari@postgresql.org>)
 id 1WRyYo-00061h-Qs
 for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Mar 2014 06:40:38 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <er@xs4all.nl>) id 1WRyYn-00061T-7H
 for pgsql-hackers@postgresql.org; Mon, 24 Mar 2014 06:40:37 +0000
Received: from smtp-vbr1.xs4all.nl ([194.109.24.21])
 by magus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <er@xs4all.nl>) id 1WRyYk-0005e2-S7
 for pgsql-hackers@postgresql.org; Mon, 24 Mar 2014 06:40:36 +0000
Received: from webmail.xs4all.nl (dovemail17.xs4all.nl [194.109.26.19])
 by smtp-vbr1.xs4all.nl (8.13.8/8.13.8) with ESMTP id s2O6eXgh026046
 for <pgsql-hackers@postgresql.org>; Mon, 24 Mar 2014 07:40:33 +0100 (CET)
 (envelope-from er@xs4all.nl)
Received: from 83.163.19.29 (SquirrelMail authenticated user er)
 by webmail.xs4all.nl with HTTP; Mon, 24 Mar 2014 07:40:33 +0100
Message-ID: <8baa40942b7a19618668ada3779e209a.squirrel@webmail.xs4all.nl>
Date: Mon, 24 Mar 2014 07:40:33 +0100
Subject: typos
From: "Erik Rijkers" <er@xs4all.nl>
To: pgsql-hackers@postgresql.org
User-Agent: SquirrelMail/1.4.18
MIME-Version: 1.0
Content-Type: multipart/mixed;boundary="----=_20140324074033_55351"
X-Virus-Scanned: by XS4ALL Virus Scanner
X-Pg-Spam-Score: -2.4 (--)
List-Archive: <http://archives.postgresql.org/pgsql-hackers>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-hackers.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@postgresql.org>
List-Post: <mailto:pgsql-hackers@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-hackers>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
X-Mailing-List: pgsql-hackers
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

------=_20140324074033_55351
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

A few 'the the' typos in code & docs.
------=_20140324074033_55351
Content-Type: text/x-diff; name="thethe.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="thethe.patch"

--- src/backend/access/transam/xlog.c.orig	2014-03-23 22:43:44.864504319 +0100
+++ src/backend/access/transam/xlog.c	2014-03-23 22:44:02.735634100 +0100
@@ -1089,7 +1089,7 @@
 	 * has progressed. There is a small fixed number of insertion locks,
 	 * determined by the num_xloginsert_locks GUC. When an inserter crosses a
 	 * page boundary, it updates the value stored in the lock to the how far it
-	 * has inserted, to allow the the previous buffer to be flushed.
+	 * has inserted, to allow the previous buffer to be flushed.
 	 *
 	 * Holding onto an insertion lock also protects RedoRecPtr and
 	 * fullPageWrites from changing until the insertion is finished.
--- doc/src/sgml/json.sgml.orig	2014-03-23 22:44:19.622807673 +0100
+++ doc/src/sgml/json.sgml	2014-03-23 22:44:37.082954235 +0100
@@ -24,7 +24,7 @@
   There are two JSON data types: <type>json</> and <type>jsonb</>.
   Both accept <emphasis>almost</emphasis> identical sets of values as
   input.  The major practical difference is one of efficiency.  The
-  <type>json</> data type stores an exact copy of the the input text,
+  <type>json</> data type stores an exact copy of the input text,
   which processing functions must continually reparse, while
   <type>jsonb</> data is stored in a decomposed binary format that
   makes it slightly less efficient to input due to added serialization
--- doc/src/sgml/logicaldecoding.sgml.orig	2014-03-23 22:44:54.198118825 +0100
+++ doc/src/sgml/logicaldecoding.sgml	2014-03-23 22:45:14.746112339 +0100
@@ -169,7 +169,7 @@
     </indexterm>
     <title>Logical Decoding</title>
     <para>
-     Logical decoding is the the process of extracting all persistent changes
+     Logical decoding is the process of extracting all persistent changes
      to a database's tables into a coherent, easy to understand format which
      can be interpreted without detailed knowledge of the database's internal
      state.
------=_20140324074033_55351
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

------=_20140324074033_55351--