Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZSXt-0007Rm-PY for pgsql-admin@arkaria.postgresql.org; Thu, 11 Jan 2018 02:24:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZSXt-0000H7-3Q for pgsql-admin@arkaria.postgresql.org; Thu, 11 Jan 2018 02:24:45 +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 1eZSXs-0000Gv-9E for pgsql-admin@lists.postgresql.org; Thu, 11 Jan 2018 02:24:44 +0000 Received: from resqmta-po-02v.sys.comcast.net ([2001:558:fe16:19:96:114:154:161]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eZSXo-00046M-Lo for pgsql-admin@postgresql.org; Thu, 11 Jan 2018 02:24:42 +0000 Received: from resomta-po-15v.sys.comcast.net ([96.114.154.239]) by resqmta-po-02v.sys.comcast.net with ESMTP id ZSX2em0uejqJfZSXmeR8zv; Thu, 11 Jan 2018 02:24:38 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1515637478; bh=c/Olqi2cdTmw3KTr5TK4mB/O2w+MjgdmGSWzd4XryxU=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=gwlvLWIxPkDL9Bqf4cJyqWiDUE7n+qUneY88Oro6Eh3qe4FZzyQ9KeA4AsFD8nqap 3l5Nz0L5CepX/w7Tg2TYzPPoMIbW+d3Qx993B3eO1aBnc+5pSRSMW+7hoQjgOAcBOc yAxAIT+E1WllqYbSD7gkLhrIbebCmPxbb8Peh5CCvk6ACoWaFrDQ5TayjVld0CllDC kWdD+eRpCzHyNCillPXlZm6Dr23enmMCnlxJXHcCJHv0D9oKIomVyjcTZ0PnpCSNyO gT452dSQhzAED3lCSR9w3oApMkT43khQPCbqBKylaLqKQ7MFcsTk42kn1Xw7dlXDEc ZG9NxRHji/sjA== Received: from jsievers.comcast.net ([12.187.116.132]) by resomta-po-15v.sys.comcast.net with SMTP id ZSXdeATdscGWFZSXgehKL3; Thu, 11 Jan 2018 02:24:36 +0000 Received: from jsievers.enova.com (localhost [127.0.0.1]) by jsievers.comcast.net (Postfix) with ESMTP id 92E9B26005E for ; Wed, 10 Jan 2018 20:24:29 -0600 (CST) From: Jerry Sievers To: pgsql-admin@postgresql.org Subject: pg_receivexlog only captures WAL data, not *.backup? Date: Wed, 10 Jan 2018 20:24:29 -0600 Message-ID: <87inc9ceua.fsf@jsievers.enova.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-CMAE-Envelope: MS4wfICTL6IzJNH/XypT1/3LnZtVuuIoeY+JBrdBLcScF0gKGeM9ta+7J0VEAbkkWlUgDk8QkiSbo4m4pPOSCG5wWgQeF9k8wmytB1cBJ/yIHBxkbJliv8Xs idFM1Erno6WmY/0DMMEKhf6ZF1gRR9nldaW7DpJDl2bEtjT7JAwLE5gXag3A1qTEGb7AzQt965Re/w== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is on 9.6 and I have not tested on 10 yet. The docs mention being able to use pg_receivexlog in stead of archive_command as main backup method, I wonder how this is possible? I did observe that no such *.backup file gets copied by pg_receivexlog after the server was put in and taken out of backup mode. It was my impression that *.backup files were required during PITR to mark the point of consistency. Is this not or no longer the case? Or, I wonder if it depends on pg_basebackup being used w/one of the options that captures all WAL as part of it? Also, I did not (yet) test to see whether timeline *.history files get copied if pg_receivexlog was pointed at a standby that was then promoted. Thanks for any insight. -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800