From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Server won't start with fallback setting by initdb. |
Date: | 2018-03-07 20:49:54 |
Message-ID: | CA+TgmobwXnYkTzOmZJJQLdz2FTfHTiikGCzALbv5VEnw9q2yCQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 6, 2018 at 10:51 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Changing the defaults to go back down strikes me as an entirely wrong
> approach after we've had a release with the higher defaults without
> seriously compelling arguments against, and I don't agree that we've had
> such a case made here. If this discussion had happened before v10 was
> released, I'd be much more open to going with the suggestion of '5', but
> forcing users to update their configs for working environments because
> we've decided that the default of 10 was too high is just pedantry, in
> my opinion.
+1. I don't see any real downside of increasing the minimum value of
max_connections to 20. I wasn't particularly a fan of raising
max_wal_senders to 10, but a lot of other people were, and so far
nobody's reported any problems related to that setting (that I know
about).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-03-07 20:58:38 | Re: RFC: Add 'taint' field to pg_control. |
Previous Message | Pavel Stehule | 2018-03-07 20:37:26 | Re: csv format for psql |