From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
---|---|
To: | Mitchell Bösecke <mitchell(dot)bosecke(at)forcorp(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_basebackup: wal streaming can only be used in plain mode |
Date: | 2015-08-05 01:44:29 |
Message-ID: | 55C16A7D.6080103@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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 <http://www.forcorp.com/>
>
> (o) 587.410.4067
> (f) 780.453.3986
From | Date | Subject | |
---|---|---|---|
Next Message | John Scalia | 2015-08-05 13:56:02 | Query runs on 9.2, but not on 9.4 |
Previous Message | Mitchell Bösecke | 2015-08-04 23:09:37 | pg_basebackup: wal streaming can only be used in plain mode |