From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_basebackup --wal-method=fetch |
Date: | 2024-02-09 14:19:35 |
Message-ID: | CABUevEwb3Gj9osaR9_PCrmYtjv+CMsEWXhoj3S5=TmCPLkhPNA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, Feb 9, 2024 at 12:11 AM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
>
> On Thu, Feb 8, 2024 at 5:21 PM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>>
>> Greetings,
>>
>> * Ron Johnson (ronljohnsonjr(at)gmail(dot)com) wrote:
>>
>> > The word "streaming".
>> > Should be "But isn't streaming the whole purpose of pg_basebackup"?
>>
>> I'm a bit confused on this point still as if the whole purpose of
>> pg_basebackup is to be streaming ... then we should be defaulting to
>> fetch mode still?
>
>
> No. Since I thought streaming is the whole purpose of pg_basebackup, I questioned the utility of every other method except --wal-method=streaming.
Well, "fetch" mode also does streaming... It just does streaming at
the end instead of parallel. So I guess one could argue the names
chosen are wrong, and should be named something like "parallel" and
"sequential". But I think the ship on renaming that has sailed a long
time ago...
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | David Barron | 2024-02-09 17:00:57 | upgrade questions |
Previous Message | Ron Johnson | 2024-02-08 23:10:38 | Re: pg_basebackup --wal-method=fetch |