From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
Cc: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: The shared buffers challenge |
Date: | 2011-05-26 16:45:38 |
Message-ID: | BANLkTint2+qh_ZecBYZQ99m4_k_v25pF=A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, May 26, 2011 at 11:37 AM, Claudio Freire <klaussfreire(at)gmail(dot)com> wrote:
> On Thu, May 26, 2011 at 6:02 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>> The point is what we can prove, because going through the
>> motions of doing that is useful.
>
> Exactly, and whatever you can "prove" will be workload-dependant.
> So you can't prove anything "generally", since no single setting is
> best for all.
Then we should stop telling people to adjust it unless we can match
the workload to the improvement. There are some people here who can
do that as if by magic, but that's not the issue. I'm trying to
understand the why it works better for some than for others. What's
frustrating is simply believing something is the case, without trying
to understand why. How about, instead of arguing with me, coming up
with something for the challenge?
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-05-26 17:00:43 | Re: LIMIT and UNION ALL |
Previous Message | Claudio Freire | 2011-05-26 16:37:56 | Re: The shared buffers challenge |