From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_basebackup wish list |
Date: | 2016-07-28 13:16:53 |
Message-ID: | CAA4eK1Lx5jJWxtgC-6CavydCp32mWAzaKky=bSKc+GTdUt2jSg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 28, 2016 at 5:37 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
> Maybe I failed to parse his proposal. It's helpful if you elaborate it.
>
As per mail [1], it seems the proposal is not to use .tar for -Z 0.
Now here actually we are on the fence, one can argue that if user
doesn't want compression, he or she can use -F p (plain format).
OTOH, without compression getting the backup as a single .tar file
makes it simple to manage. I think there is some value in providing
.tar for -Z 0, however in that case how should we define usage of -F p
-Z 0? Shall we say with plain format -Z 0 gets ignored or throw error
or do something else? If first, then I think it is better to mention
the same in docs.
[1] - https://www.postgresql.org/message-id/CAMkU%3D1zzj0et2x9fCqxMGJ6XP-FtMSUwtNQGwF01698FRWQ6uA%40mail.gmail.com
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2016-07-28 13:48:13 | Re: [Patch] RBTree iteration interface improvement |
Previous Message | pgwhatever | 2016-07-28 13:16:33 | Re: Why we lost Uber as a user |