From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: allowing wal_level change at run time |
Date: | 2015-08-19 12:46:33 |
Message-ID: | CANP8+jJWKkcVF-CuSEAR9v_sCQuVtOWEvqXgHfFrNPbCwVqOaA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 18 August 2015 at 18:46, Andres Freund <andres(at)anarazel(dot)de> wrote:
> ISTM that it's not too hard to
> a) make archive_mode PGC_SIGHUP
> b) make wal_level PGC_SIGHUP
>
+1
> c) automatically increase wal_level to logical whenever a logical
> replication slot is defined
>
-1
It would be easier to just have wal_level = logical always, but allow it to
be set lower if desired.
Increasing wal_level dynamically might otherwise happen too late.
> it seems considerably harder to
>
> d) make max_wal_senders PGC_SIGHUP
> e) make max_replication_slots PGC_SIGHUP
>
> because they need shmem, locks, and everything.
>
>
> Therefore I propose something slightly different:
>
> We change the default of max_wal_senders, max_replication_slots, to some
> reasonably high setting
Agreed, I suggest 8 as the default for each.
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2015-08-19 12:52:39 | Re: Declarative partitioning |
Previous Message | Victor Wagner | 2015-08-19 12:41:20 | Re: Proposal: Implement failover on libpq connect level. |