pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gregory Wood <gregw@com-stock.com>
To: Jeff <threshar@torgo.978.org>
Cc: PostgreSQL-General <pgsql-general@postgresql.org>
Subject: Re: [PERFORM] One large v. many small
Date: Thu, 30 Jan 2003 14:48:16 -0500
Message-ID: <016b01c2c898$891d05c0$7889ffcc@comstock.com> (raw)
References: <Pine.BSF.4.44.0301301358190.39965-100000@torgo.978.org>

> imagine this scenario using your
> methods (with a wonderful pg performance problem in hand (unless you are
> running cvs))

<snip>

> If you do a little app tuning (maybe spend 10-30 minutes readig pgsql
> archives) you'll learn to rewrite it as an exists query and make it faster
> than it ever could have been on the fast hardware.

Your example is invalid... you're talking about an implementation detail,
not an architectural design issue.

I have to agree with the original point... normalize the database into the
proper form, then denormalize as necessary to make things perform
acceptably. In other words, do things the right way and then muck it up if
you have to.

While you make an excellent point (i.e. you can't always through hardware,
especially excessive hardware at the problem), I would err on the side of
doing things the right way. It usually ends up making the software easier to
maintain and add to. A poor design to save a few thousand dollars on
hardware now can cost many tens of thousands (or more) dollars on
programming time down the road.

I've seen entirely too many cases where people started thinking about
performance before they considered overall design. It almost always ends in
disaster (especially since hardware only gets faster over time and software
only gets more complex).

Greg




view thread (17+ messages)  latest in thread

Message-ID: <016b01c2c898$891d05c0$7889ffcc@comstock.com>
Permalink:  ../016b01c2c898$891d05c0$7889ffcc@comstock.com/
Also on:    postgresql.org/message-id/016b01c2c898$891d05c0$7889ffcc@comstock.com

 · 

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: gregw@com-stock.com, threshar@torgo.978.org, pgsql-general@postgresql.org
  Subject: Re: [PERFORM] One large v. many small
  In-Reply-To: <016b01c2c898$891d05c0$7889ffcc@comstock.com>
  References: <Pine.BSF.4.44.0301301358190.39965-100000@torgo.978.org> <016b01c2c898$891d05c0$7889ffcc@comstock.com>

* 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