Re: Moving postgresql.conf tunables into 2003...

From: Kaarel <kaarel(at)future(dot)ee>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Matthew Nuzum <cobalt(at)bearfruit(dot)org>, 'Andrew Sullivan' <andrew(at)libertyrms(dot)info>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Moving postgresql.conf tunables into 2003...
Date: 2003-07-09 18:33:35
Message-ID: 3F0C5FFF.30406@future.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>>Are you willing to say that the PostgreSQL database system should only be
>>used by DBAs? I believe that Postgres is such a good and useful tool that
>>anyone should be able to start using it with little or no barrier to entry.
>
>
> I quite agree. But there is a difference between saying "you should get
> decent performance with no effort" and "you should get optimal
> performance with no effort". I think we can get to the first with
> relatively little trouble (like boosting the default shared_buffers to
> 1000), but the second is an impractical goal.

Just wanted to repeat some of the thoughts already been expressed.

There are no reasons why shouldn't PostgreSQL be reasonably well
configured for a particular platform out of the box. Not for maximum
performance but for good enough performance. The many complaints by new
users about PostgreSQL being suprisingly slow and the all the so
standard answers (vacuum, pump up memory settings) imho prove that the
default installatio can be improved. Already mentioned in the mail
lists: using multiple standard conf files, quering system info and
dynamically generating all or some parts of the conf file, automating
the vacuum process...

Kaarel

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message scott.marlowe 2003-07-09 19:40:45 Re: Moving postgresql.conf tunables into 2003...
Previous Message Rod Taylor 2003-07-09 17:42:35 Re: Some very weird behaviour....