From: | mlw <pgsql(at)mohawksoft(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | "Adrian 'Dagurashibanipal' von Bidder" <avbidder(at)fortytwo(dot)ch>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Oracle rant |
Date: | 2003-01-16 23:09:11 |
Message-ID: | 3E273B97.3060709@mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut wrote:
>Adrian 'Dagurashibanipal' von Bidder writes:
>
>
>
>> - postgres should auto-tune itself - the *cost could perhaps be
>>adjusted after some statistics have been collected, and there should be
>>some sensible way to determine an optimal setting for the famous
>>shared_buffers (and the default should be something that gets reasonable
>>performance on common cases)
>>
>>
>
>Over the last couple of years PostgreSQL has transformed from hardly
>configurable to fully configurable. Currently we're in a mode where we
>add new configuration parameters whenever there's a degree of uncertainty.
>Sooner rather than later we need to shift to the next phase, which is as
>you say autoconfiguration, because ease of administration is one of the
>great advantages of PostgreSQL
>
I think the idea of adding a parameter when ever you are not sure, is a
great idea. That does preclude, however, the ability for a process
within PostgreSQL from analyzing the metrics and updating the parameter
file or table.
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-01-17 01:54:26 | Re: Options for growth |
Previous Message | Nigel J. Andrews | 2003-01-16 22:05:02 | Re: Indexes |