Re: max_wal_senders must die
От | Robert Haas |
---|---|
Тема | Re: max_wal_senders must die |
Дата | |
Msg-id | AANLkTi=jm0=evkve0D+UXpMfjSnW4Tx-23gFbGPRp3YW@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: max_wal_senders must die (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: max_wal_senders must die
|
Список | pgsql-hackers |
On Tue, Oct 19, 2010 at 12:18 PM, Josh Berkus <josh@agliodbs.com> wrote: > On 10/19/2010 09:06 AM, Greg Smith wrote: >> >> I think Magnus's idea to bump the default to 5 triages the worst of the >> annoyance here, without dropping the feature (which has uses) or waiting >> for new development to complete. I'd be in favor of just committing >> that change right now, before it gets forgotten about, and then if >> nobody else gets around to further work at least something improved here >> for 9.1. > > Heck, even *I* could write that patch, if we're agreed. Although you can > commit it. Setting max_wal_senders to a non-zero value causes additional work to be done every time a transaction commits, aborts, or is prepared. It's possible that this overhead is too trivial to be worth worrying about; I haven't looked at it closely. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: