Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-docs-owner+M7949=pgsql+2Ddocs=arkaria.postgresql.org@postgresql.org>)
 id 1WS2XG-00066s-4R
 for pgsql-docs@arkaria.postgresql.org; Mon, 24 Mar 2014 10:55:18 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-docs-owner+M7949=pgsql+2Ddocs=arkaria.postgresql.org@postgresql.org>)
 id 1WS2XF-0007ha-H8
 for pgsql-docs@arkaria.postgresql.org; Mon, 24 Mar 2014 10:55:17 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <masao.fujii@gmail.com>) id 1WS2XE-0007hN-VP
 for pgsql-docs@postgresql.org; Mon, 24 Mar 2014 10:55:17 +0000
Received: from mail-pd0-x22f.google.com ([2607:f8b0:400e:c02::22f])
 by magus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <masao.fujii@gmail.com>) id 1WS2X7-0001o4-NW
 for pgsql-docs@postgresql.org; Mon, 24 Mar 2014 10:55:16 +0000
Received: by mail-pd0-f175.google.com with SMTP id x10so5181435pdj.20
 for <pgsql-docs@postgresql.org>; Mon, 24 Mar 2014 03:55:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=KfM6twa8f9vwHVUVKIatnLmSWplodsMRSr/TJxO49vU=;
 b=ojb5UkB276zEMijlXM+evc9z7c76lh21Dj4/Se8T32sE0BGM63hMoSyfmu0Zn5uYmQ
 wiy67h7/sjSRB+6UIWslJ8qhH0SzIUCRQSTZ3XaCnhB5eiUh6IYYxc+9GnpzJpi0CSJ3
 uKdjoCwvG6naGJ7zWpY76pLa8M+WFEnqO7XDH9/9PXLPEo96OFrV7+Xi+Bkbvxrs/doZ
 0CTDNeVBDCC9tzOP3LJ8APQtpbmGzBrplHGiYeG+pnOa6PhdzqcpLVi9lP5z/tk8F8cY
 SleRPRCksadddN1mq32DOmfAyVvSoX0/qKGfyuw1zAdTHNqp0ezCEY5wzrBWTvzWJk5I
 1LCQ==
MIME-Version: 1.0
X-Received: by 10.66.27.202 with SMTP id v10mr7982122pag.127.1395658508124;
 Mon, 24 Mar 2014 03:55:08 -0700 (PDT)
Received: by 10.70.53.8 with HTTP; Mon, 24 Mar 2014 03:55:08 -0700 (PDT)
In-Reply-To: <532D62A1.3010309@joh.to>
References: <532D62A1.3010309@joh.to>
Date: Mon, 24 Mar 2014 19:55:08 +0900
Message-ID: 
 <CAHGQGwFwiYGnc4JsebcbCE3pa83mUDjP7=awVUqiFLhMJ9eDWQ@mail.gmail.com>
Subject: Re: START_REPLICATION TIMELINE
From: Fujii Masao <masao.fujii@gmail.com>
To: Marko Tiikkaja <marko@joh.to>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-docs>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-docs.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@postgresql.org>
List-Post: <mailto:pgsql-docs@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-docs>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
X-Mailing-List: pgsql-docs
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On Sat, Mar 22, 2014 at 7:14 PM, Marko Tiikkaja <marko@joh.to> wrote:
> Hi,
>
> In http://www.postgresql.org/docs/devel/static/protocol-replication.html
> there's conflicting information about the TIMELINE option.  In the syntax
> part it's not optional, but the text says "If specified, streaming starts on
> timeline tli; otherwise, the server's current timeline is selected.".  Looks
> like the 9.3 docs always require a timeline to be specified.

ISTM that TIMELINE is optional both in HEAD and 9.3. So I fixed the document
in both versions. Thanks for the report!

Regards,

-- 
Fujii Masao


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