Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZMnmv-0008TJ-Gg for pgsql-admin@arkaria.postgresql.org; Wed, 05 Aug 2015 01:46:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZMnmv-0000j6-2C for pgsql-admin@arkaria.postgresql.org; Wed, 05 Aug 2015 01:46:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZMnlI-0007HR-7N for pgsql-admin@postgresql.org; Wed, 05 Aug 2015 01:44:56 +0000 Received: from mail-ig0-x22e.google.com ([2607:f8b0:4001:c05::22e]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZMnlE-0000Sd-Jl for pgsql-admin@postgresql.org; Wed, 05 Aug 2015 01:44:55 +0000 Received: by igbpg9 with SMTP id pg9so105366176igb.0 for ; Tue, 04 Aug 2015 18:44:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=ozp3stU0WJmYttNPxBJJX4Jqn835t7QV/Qnyf3uosw8=; b=N++5JZWph3EkMyFD786TB0NOiJ5QShnyN5UZ1NFAZ86kJsjT4uRdX8kzjUInBys748 CgqRH96sTn+jLfncf3jHenwaVEgfqsVR76cTl9co/SL/PxgXiY2Xi/rzz+CyW2lcFI3N ttWbChcGFJ/QGeoLYpcKY5w9DaNaK9nquhgjXaj64U7ZdioTrsRMRdzMmTreEh6orHhF 7CP4TiyCNhKg+kvuvL/udwL/u7EewMpdUyzULZgtdpeU0OPCMfWmyQ17bYepzqVrUXA4 63nPaWOMqYq4DYNyzdn70trGvQoQVrfVqflxMx2qaJ0XS0W0ymWfI00gFvQeNB6lf86A gttA== X-Received: by 10.50.78.99 with SMTP id a3mr7581493igx.29.1438739090470; Tue, 04 Aug 2015 18:44:50 -0700 (PDT) Received: from [192.168.0.2] (cpe-72-182-26-34.austin.res.rr.com. [72.182.26.34]) by smtp.gmail.com with ESMTPSA id r95sm957442ioi.38.2015.08.04.18.44.49 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Aug 2015 18:44:49 -0700 (PDT) Message-ID: <55C16A7D.6080103@gmail.com> Date: Tue, 04 Aug 2015 20:44:29 -0500 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: =?UTF-8?B?TWl0Y2hlbGwgQsO2c2Vja2U=?= , pgsql-admin@postgresql.org Subject: Re: pg_basebackup: wal streaming can only be used in plain mode References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------030708080009010507030405" X-Pg-Spam-Score: -2.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. --------------030708080009010507030405 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Mitchell, If you look in the documentation, you'll see that the streaming mode requires a second replication connection. So, how would you integrate two separate channels into one tar input? Also, as the stream and backup aren't synchronized, there wouldn't be any way to isolate those in a tarball. True, they don't explicitly call this out, but if you think about it only the -X f mode (fetch) makes any sense. This is why I always use the fetch mode when writing to tar. FWIW, Jay On 8/4/2015 6:09 PM, Mitchell Bösecke wrote: > Hi, > > In regards to pg_basebackup, I want to use "--format=tar" (for the purpose of sending the backup to stdout) but when I also try to use "--xlog-method=stream" to include some WAL > files (without worrying about the wal_keep_segment parameter on the server) it tells me "wal streaming can only be used in plain mode". > > I can't find any documentation regarding this conflict between "--format=tar" and "--xlog-method=stream". Can anyone provide any insight into why this combination is forbidden, > or where it might be documented? Are there plans to support this combination in the future? > > Thanks for any help > > -- > Mitchell Bosecke, B.Sc. > Software Developer > > FORCORP > #101, 11710 Kingsway NW > Edmonton , AB, T5G 0X5 > www.forcorp.com > > (o) 587.410.4067 > (f) 780.453.3986 --------------030708080009010507030405 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Mitchell,

If you look in the documentation, you'll see that the streaming mode requires a second replication connection. So, how would you integrate two separate channels into one tar input? Also, as the stream and backup aren't synchronized, there wouldn't be any way to isolate those in a tarball. True, they don't explicitly call this out, but if you think about it only the -X f mode (fetch) makes any sense. This is why I always use the fetch mode when writing to tar.

FWIW,
Jay

On 8/4/2015 6:09 PM, Mitchell Bösecke wrote:
Hi,

In regards to pg_basebackup, I want to use "--format=tar" (for the purpose of sending the backup to stdout) but when I also try to use "--xlog-method=stream" to include some WAL files (without worrying about the wal_keep_segment parameter on the server) it tells me "wal streaming can only be used in plain mode".

I can't find any documentation regarding this conflict between "--format=tar" and "--xlog-method=stream". Can anyone provide any insight into why this combination is forbidden, or where it might be documented? Are there plans to support this combination in the future?

Thanks for any help

--
Mitchell Bosecke, B.Sc.
Software Developer

FORCORP
#101, 11710 Kingsway NW
Edmonton , AB, T5G 0X5

(o) 587.410.4067
(f) 780.453.3986

--------------030708080009010507030405--