From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: max_wal_senders must die |
Date: | 2010-11-13 04:09:06 |
Message-ID: | 201011130409.oAD496x22133@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Josh Berkus wrote:
>
> > None of us know. What I do know is that I don't want PostgreSQL to be
> > slower out of the box.
>
> Understandable. So it seems like the answer is getting replication down
> to one configuration variable for the common case. That eliminates the
> cycle of "oops, need to set X and restart/reload" without paying
> performance penalties on standalone servers.
Right. I propose that we set max_wal_senders to unlimited when
wal_level = hot_standby. When they tell us they are using hot_standby
via wal_level, why make them change another setting (max_wal_senders)?
Basically, we don't need to turn everything on by default, but some
settings should trigger other behavior automatically.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-13 04:25:21 | Re: pgsql: Improved parallel make support |
Previous Message | Tom Lane | 2010-11-13 03:55:54 | Re: plan time of MASSIVE partitioning ... |