Re: Doc patch making firm recommendation for setting the value of commit_delay
От | Peter Geoghegan |
---|---|
Тема | Re: Doc patch making firm recommendation for setting the value of commit_delay |
Дата | |
Msg-id | CAEYLb_WmuYuV_K+RatgbkLZ99NH1UY-4=HND9Nieiko5upsOew@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Doc patch making firm recommendation for setting the value of commit_delay (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: Doc patch making firm recommendation for setting the
value of commit_delay
Re: Doc patch making firm recommendation for setting the value of commit_delay |
Список | pgsql-hackers |
On 15 November 2012 10:04, Magnus Hagander <magnus@hagander.net> wrote: >> I would rather see this just turn into one of the things a more general >> tuning tool knew how to do, executing against a fully setup system. Having a >> useful implementation of commit_delay and useful docs on it seems like >> enough of a jump forward for one release. Moving fully into auto-tuning >> before getting more field feedback on how that works out is pretty >> aggressive. > > +1. I am inclined to agree. I did attempt to use the instrumentation macros to have commit_delay set adaptively at runtime, which would have at least addressed this concern, but that just didn't work as well as this. -- Peter Geoghegan http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training and Services
В списке pgsql-hackers по дате отправления: