On 15 November 2012 10:04, Magnus Hagander <mag...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
