From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
Subject: | Re: Replication/backup defaults |
Date: | 2017-01-04 14:46:10 |
Message-ID: | CABUevEyUZN63_zXtZM5EoYkq55TDUge9vvRbD7V288cOFWuJ-w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 4, 2017 at 3:43 PM, Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 12/31/16 10:00 AM, Magnus Hagander wrote:
> > max_wal_senders=10
> > max_replication_slots=20
>
> How about we default max_replication_slots to -1, which means to use the
> same value as max_wal_senders?
>
> I think this would address the needs of 99% of users. If we do like you
> suggest, there are going to be very many users who forget to adjust
> these two values together, and very many who will do it but will be
> puzzled and annoyed by it. Since we're now pushing the use of
> replication slots even more (your pg_basebackup change, upcoming logical
> replication), I think this could be a major source of misconfigurations.
>
But you don't necessarily want to adjust them together, do you? They are
both capped by max_connections, but I don't think they have any other
direct relation between each other?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-01-04 14:47:10 | Re: [PATCH] Reload SSL certificates on SIGHUP |
Previous Message | Peter Eisentraut | 2017-01-04 14:43:03 | Re: Replication/backup defaults |