Re: clog_buffers to 64 in 8.3?

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Josh Berkus" <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: clog_buffers to 64 in 8.3?
Date: 2007-08-04 08:57:36
Message-ID: 1186217856.4172.21.camel@ebony.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2007-08-03 at 18:16 -0400, Tom Lane wrote:

> In any case this is getting pretty darn far away from a one-liner patch.
> I think it needs more thought and more testing than we can spare now.

Agreed.

We're much further behind with this release than ever before, so we need
to put the cut somewhere.

Once the major features are in, we do need a period of secondary/final
tuning. For the *next* release, I would like to plan for a Tuning Month
somewhere in the release process. That would allow some formal way of
handling this kind of thing, 'cos we seem to hit the "its too late for
this kind of change" fairly regularly. Also, the more we tune, the more
performance regressions occur, so we'll need to start formally checking
for those too.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2007-08-04 10:32:31 Re: .NET driver
Previous Message Rohit Khare 2007-08-04 04:57:47 Re: .NET driver