Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1clLm6-00014r-GF for pgsql-admin@arkaria.postgresql.org; Tue, 07 Mar 2017 20:32:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1clLm5-0008IC-RJ for pgsql-admin@arkaria.postgresql.org; Tue, 07 Mar 2017 20:32:01 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1clLm4-0008DY-Kq for pgsql-admin@postgresql.org; Tue, 07 Mar 2017 20:32:00 +0000 Received: from omr1.cc.ipv6.vt.edu ([2607:b400:92:8300:0:c6:2117:b0e] helo=omr1.cc.vt.edu) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1clLm1-0002pV-Tg for pgsql-admin@postgresql.org; Tue, 07 Mar 2017 20:31:59 +0000 Received: from mr3.cc.vt.edu (mr3.cc.vt.edu [IPv6:2607:b400:92:8500:0:7f:b804:6b0a]) by omr1.cc.vt.edu (8.14.4/8.14.4) with ESMTP id v27KVu0g031395 for ; Tue, 7 Mar 2017 15:31:56 -0500 Received: from mail-qk0-f198.google.com (mail-qk0-f198.google.com [209.85.220.198]) by mr3.cc.vt.edu (8.14.7/8.14.7) with ESMTP id v27KVp5t031199 for ; Tue, 7 Mar 2017 15:31:56 -0500 Received: by mail-qk0-f198.google.com with SMTP id j127so25344719qke.2 for ; Tue, 07 Mar 2017 12:31:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version; bh=c/9DPv7aLwLDWOtxWpipUDDv39j/6eGZL/HXcXx65ig=; b=TO2YYqzX1CHI+KaK4QZqqwMbujEF7aT8sOIHN57F6de/5O4+/WNlTH87+yNt0zzWDg ytDNnb6iCRX9aBcJh3MwHv2S4Q17YkpXE6sAFusuI3f4k00puw+XWjb2G4WqoyezZRW8 6vKm0vH2RwijfKKCA/Bnf8qvmlBnzxb0M2nRFHmwRdHqETwHYmfpY/dkZpwwK+icqaIJ 1uUnh2LAmulAhq+Cjf5BVuToonUKQ/LmtZBaTlQYdq51fEI01Yx46K8i/M6IvdB0+iNR 19LUxq749RDam1xx2zJpwLXH54u1/LsjWZr+TUMjEq9dfJetrhgy0TbQArFAgnQPQi0C gzgA== X-Gm-Message-State: AMke39lDKBRm4c6yyLAoyVZGOUjlqv8J1xKDRYzYCNuGil0fc3i7Bf4UXwYbZ8r7YpBiCsz6Ffj3Xm6Rgv46r8YbYORVgUiiWOsT05Wh4lqaw9zginhNFI0Mm+BF684nJBlWyYsJRYsNq5zMd9W67kdWrwT0HtKoACYI8Y/3QpEDgewzpMw64+ZfEy3eBWPYzljsMrE= X-Received: by 10.200.49.29 with SMTP id g29mr2814249qtb.275.1488918677103; Tue, 07 Mar 2017 12:31:17 -0800 (PST) X-Received: by 10.200.49.29 with SMTP id g29mr2814203qtb.275.1488918676764; Tue, 07 Mar 2017 12:31:16 -0800 (PST) Received: from stell.cns.vt.edu ([2001:468:c80:2102:29bf:a381:cd7b:2143]) by smtp.gmail.com with ESMTPSA id c19sm716775qtc.29.2017.03.07.12.31.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Mar 2017 12:31:16 -0800 (PST) To: "pgsql-admin@postgresql.org" From: Ray Stell Subject: pg_basebackup recovery failure Message-ID: Date: Tue, 7 Mar 2017 15:31:16 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------A5BC4039A3968F10CC3FF65C" X-Spam-Status: No, score=1.0 required=5.0 tests=HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_SOFTFAIL autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mr3.cc.vt.edu X-Pg-Spam-Score: -3.7 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org This is a multi-part message in MIME format. --------------A5BC4039A3968F10CC3FF65C Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On this doc page are some command examples for pg_basebackup: https://www.postgresql.org/docs/current/static/app-pgbasebackup.html such as: pg_basebackup -h mydbserver -D /usr/local/pgsql/data I've never gotten this to work. When I bring up the copy on an intended standby system I always get the classic: PANIC: could not locate a valid checkpoint record Failing that, I backed up with pg_start_backup/tar/pg_stop_backup as an alternative, but I was always curious what I was doing wrong. The wiki page on setting up replication: https://wiki.postgresql.org/wiki/Streaming_Replication says use the command with this options: pg_basebackup -h 192.168.0.10 -D /srv/pgsql/standby -P -U replication --xlog-method=stream and I stumbled into option: --checkpoint=fast The standby was able to recover when I used one of these, I don't remember which, maybe both. Should the doc be updated or am I missing something? --------------A5BC4039A3968F10CC3FF65C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

On this doc page are some command examples for pg_basebackup:

        https://www.postgresql.org/docs/current/static/app-pgbasebackup.html

such as: 

    pg_basebackup -h mydbserver -D /usr/local/pgsql/data

I've never gotten this to work.  When I bring up the copy on an intended standby system I always get the classic:

	PANIC:  could not locate a valid checkpoint record
Failing that, I backed up with pg_start_backup/tar/pg_stop_backup as an alternative, but I was always curious what I was doing wrong. 
The wiki page on setting up replication:
 
     https://wiki.postgresql.org/wiki/Streaming_Replication

says use the command with this options:
   
     pg_basebackup -h 192.168.0.10 -D /srv/pgsql/standby -P -U replication --xlog-method=stream

and I stumbled into option:

      --checkpoint=fast

The standby was able to recover when I used one of these, I don't remember which, maybe both. 

Should the doc be updated or am I missing something?
     
--------------A5BC4039A3968F10CC3FF65C--