pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Frank Wiles <frank@wiles.org>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: rjpeace@earthlink.net
Cc: yves.vindevogel@implements.be
Cc: pgsql-performance@postgresql.org
Subject: Re: Some help on buffers and other performance tricks
Date: Wed, 9 Nov 2005 18:54:50 -0600
Message-ID: <20051109185450.2f20275d.frank@wiles.org> (raw)
In-Reply-To: <20051110004332.GE8230@surnet.cl>
References: <17035565.1131571489652.JavaMail.root@elwamui-hound.atl.sa.earthlink.net>
	<20051109230752.GC8230@surnet.cl>
	<20051109175332.3edbd5fc.frank@wiles.org>
	<20051110004332.GE8230@surnet.cl>

On Wed, 9 Nov 2005 21:43:33 -0300
Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:

> Frank Wiles wrote:
> 
> >   Obviously there are systems/datasets/quantities where this won't
> >   always work out best, but for the majority of systems out there 
> >   complicating your schema, maxing your hardware, and THEN tuning
> >   is IMHO the wrong approach. 
> 
> I wasn't suggesting to complicate the schema -- I was actually
> thinking in systems where some queries are not using indexes, some
> queries are plain wrong, etc.  Buying a very expensive RAID and then
> noticing that you just needed to create an index, is going to make
> somebody feel at least somewhat stupid.

  Sorry I was referring to Ron statement that the first step should
  be to "Optimize your schema to be as tight as possible." 

  But I agree, finding out you need an index after spending $$$ on 
  extra hardware would be bad.  Especially if you have to explain it
  to the person forking over the $$$! :) 

 ---------------------------------
   Frank Wiles <frank@wiles.org>
   http://www.wiles.org
 ---------------------------------




view thread (11+ messages)  latest in thread

Message-ID: <20051109185450.2f20275d.frank@wiles.org>
Permalink:  ../20051109185450.2f20275d.frank@wiles.org/
Also on:    postgresql.org/message-id/20051109185450.2f20275d.frank@wiles.org

 · 

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: frank@wiles.org, alvherre@alvh.no-ip.org, rjpeace@earthlink.net, yves.vindevogel@implements.be
  Subject: Re: Some help on buffers and other performance tricks
  In-Reply-To: <20051109185450.2f20275d.frank@wiles.org>
  References: <17035565.1131571489652.JavaMail.root@elwamui-hound.atl.sa.earthlink.net> <20051109230752.GC8230@surnet.cl> <20051109175332.3edbd5fc.frank@wiles.org> <20051110004332.GE8230@surnet.cl> <20051109185450.2f20275d.frank@wiles.org>

* 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