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

От: Jim C. Nasby
Тема: Re: Moving postgresql.conf tunables into 2003...
Дата: ,
Msg-id: 20030707214048.GC69704@nasby.net
(см: обсуждение, исходный текст)
Ответ на: Re: Moving postgresql.conf tunables into 2003...  (Chris Travers)
Список: pgsql-performance

Скрыть дерево обсуждения

Moving postgresql.conf tunables into 2003...  (Sean Chittenden, )
 Re: Moving postgresql.conf tunables into 2003...  (Rod Taylor, )
  Re: Moving postgresql.conf tunables into 2003...  (Sean Chittenden, )
 Re: Moving postgresql.conf tunables into 2003...  ("scott.marlowe", )
  Re: Moving postgresql.conf tunables into 2003...  (Brian Hirt, )
   Re: Moving postgresql.conf tunables into 2003...  (Sean Chittenden, )
    Re: Moving postgresql.conf tunables into 2003...  (Matthew Hixson, )
  Re: Moving postgresql.conf tunables into 2003...  (Sean Chittenden, )
   Re: Moving postgresql.conf tunables into 2003...  (Tom Lane, )
    Re: Moving postgresql.conf tunables into 2003...  (Sean Chittenden, )
 Re: Moving postgresql.conf tunables into 2003...  ("Michael Mattox", )
  Re: Moving postgresql.conf tunables into 2003...  (Sean Chittenden, )
   Re: Moving postgresql.conf tunables into 2003...  (Martin Foster, )
   Re: Moving postgresql.conf tunables into 2003...  (Bruce Momjian, )
 Re: Moving postgresql.conf tunables into 2003...  (Ron, )
 Re: Moving postgresql.conf tunables into 2003...  (Tom Lane, )
  Re: Moving postgresql.conf tunables into 2003...  (Sean Chittenden, )
   Re: Moving postgresql.conf tunables into 2003...  (Rod Taylor, )
   Re: Moving postgresql.conf tunables into 2003...  (Manfred Koizar, )
    Re: Moving postgresql.conf tunables into 2003...  (Sean Chittenden, )
     Re: Moving postgresql.conf tunables into 2003...  (Manfred Koizar, )
      Re: Moving postgresql.conf tunables into 2003...  (Sean Chittenden, )
       Re: Moving postgresql.conf tunables into 2003...  (Tom Lane, )
        Index correlation (was: Moving postgresql.conf tunables into 2003... )  (Manfred Koizar, )
     Use of multipart index with "IN"  (Rob Messer, )
      Re: Use of multipart index with "IN"  (Tom Lane, )
 Re: Moving postgresql.conf tunables into 2003...  (Josh Berkus, )
  Re: Moving postgresql.conf tunables into 2003...  (Tom Lane, )
  Re: Moving postgresql.conf tunables into 2003...  (Tom Lane, )
  Re: Moving postgresql.conf tunables into 2003...  (Tom Lane, )
  Re: Moving postgresql.conf tunables into 2003...  (Sean Chittenden, )
   Re: Moving postgresql.conf tunables into 2003...  (Josh Berkus, )
    Re: Moving postgresql.conf tunables into 2003...  (Sean Chittenden, )
     Re: Moving postgresql.conf tunables into 2003...  (Josh Berkus, )
   Re: Moving postgresql.conf tunables into 2003...  ("Matthew Nuzum", )
    Re: Moving postgresql.conf tunables into 2003...  (Michael Pohl, )
     Re: Moving postgresql.conf tunables into 2003...  (Martin Foster, )
     Re: Moving postgresql.conf tunables into 2003...  (Bruce Momjian, )
    Re: Moving postgresql.conf tunables into 2003...  (Chris Travers, )
     Re: Moving postgresql.conf tunables into 2003...  ("Jim C. Nasby", )
   Re: Moving postgresql.conf tunables into 2003...  (Andrew Sullivan, )
    Re: Moving postgresql.conf tunables into 2003...  ("Matthew Nuzum", )
     Re: Moving postgresql.conf tunables into 2003...  ("Michael Mattox", )
     Re: Moving postgresql.conf tunables into 2003...  (Tom Lane, )
      Re: Moving postgresql.conf tunables into 2003...  (Kaarel, )
       Re: Moving postgresql.conf tunables into 2003...  ("scott.marlowe", )
        Re: Moving postgresql.conf tunables into 2003...  (Martin Foster, )
  Re: Moving postgresql.conf tunables into 2003...  ("Matthew Nuzum", )

On Mon, Jul 07, 2003 at 10:08:50AM -0700, Chris Travers wrote:
> In my opinion, a serious RDBMS system will *always* require the admin to
> be doing research in order to learn how to use it effectively.  We are
> not talking about a word processor here.
>
> That being said, I think that a good part of the problem is that admins
> don't know where to look for the appropriate documentation and what is
> needed.  Expecting someone to spend 20 seconds looking for a piece of
> info is not too bad, but expecting them to spend hours trying to figure
> out what info is relavent is not going to get us anywhere.

Something else to consider is that this is made worse because tuning for
pgsql is quite different than tuning for something like Oracle or DB2,
which don't deal as much with metrics such as random access cost v.
sequential access. They also take the approach of 'give me as much
memory as you can; I'll take it from there, thankyouverymuch', which
makes effective_cache_size a bit of a mystery.
--
Jim C. Nasby, Database Consultant                  
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"


В списке pgsql-performance по дате сообщения:

От: "Matthew Nuzum"
Дата:
Сообщение: Re: Extreme high load averages
От: "scott.marlowe"
Дата:
Сообщение: Re: Extreme high load averages