| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Switch pg_basebackup to use -X stream instead of -X fetch by default? |
| Date: | 2014-08-26 16:40:27 |
| Message-ID: | CABUevEyq6_BZu7J3=COVi1imEJ_Ob3mtJw6LDLjtTPrsAMnMKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 25, 2014 at 1:35 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> Hi,
>
> currently pg_basebackup uses fetch mode when only -x is specified -
> which imo isn't a very good thing to use due to the increased risk of
> not fetching everything.
> How about switching to stream mode for 9.5+?
I think the original reasons were to not change the default behaviour
with a new feature, and secondly because defaulting to -X requires two
replication connections rather than one.
I think the first reason is gone now, and the risk/damage of the two
connections is probably smaller than running out of WAL. -x is a good
default for smaller systems, but -X is a safer one for bigger ones. So
I agree that changing the default mode would make sense.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-08-26 16:51:55 | Re: Switch pg_basebackup to use -X stream instead of -X fetch by default? |
| Previous Message | Alvaro Herrera | 2014-08-26 16:19:11 | Re: Per table autovacuum vacuum cost limit behaviour strange |