pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kaarel <kaarel@future.ee>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Matthew Nuzum <cobalt@bearfruit.org>
Cc: Andrew Sullivan <andrew@libertyrms.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: Moving postgresql.conf tunables into 2003...
Date: Wed, 09 Jul 2003 21:33:35 +0300
Message-ID: <3F0C5FFF.30406@future.ee> (raw)
In-Reply-To: <19041.1057584643@sss.pgh.pa.us>
References: <008301c34489$4dbf0b00$a322fea9@mattspc>
	<19041.1057584643@sss.pgh.pa.us>

>>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




view thread (45+ messages)  latest in thread

Message-ID: <3F0C5FFF.30406@future.ee>
Permalink:  ../3F0C5FFF.30406@future.ee/
Also on:    postgresql.org/message-id/3F0C5FFF.30406@future.ee

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: kaarel@future.ee, tgl@sss.pgh.pa.us, cobalt@bearfruit.org, andrew@libertyrms.info
  Subject: Re: Moving postgresql.conf tunables into 2003...
  In-Reply-To: <3F0C5FFF.30406@future.ee>
  References: <008301c34489$4dbf0b00$a322fea9@mattspc> <19041.1057584643@sss.pgh.pa.us> <3F0C5FFF.30406@future.ee>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox