pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: David Fetter <david@fetter.org>
Cc: mark overmeer <markovermeer@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: schema design question
Date: Sun, 19 Aug 2007 20:26:58 +0200
Message-ID: <20070819182658.GC25214@uio.no> (raw)
In-Reply-To: <20070819181216.GK28490@fetter.org>
References: <ea41f7570708190619u6daf7cep96430d20566d6159@mail.gmail.com>
	<20070819181216.GK28490@fetter.org>

On Sun, Aug 19, 2007 at 11:12:16AM -0700, David Fetter wrote:
> There's your mistake.  EAV is not performant, and won't become so.

It sort of depends. I put all the EXIF information for my image gallery into
an EAV table -- it was the most logical format at the time, although I'm not
sure I need all the information. Anyhow, with clustering and indexes,
Postgres zips through the five million records easily enough for my use -- at
least fast enough that I can live with it without feeling the need for a
redesign.

As a general database design paradigm, though, I fully agree with you.
Databases are databases, not glorified OO data stores or hash tables.

/* Steinar */
-- 
Homepage: http://www.sesse.net/



view thread (10+ messages)  latest in thread

Message-ID: <20070819182658.GC25214@uio.no>
Permalink:  ../20070819182658.GC25214@uio.no/
Also on:    postgresql.org/message-id/20070819182658.GC25214@uio.no

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: sgunderson@bigfoot.com, david@fetter.org, markovermeer@gmail.com
  Subject: Re: schema design question
  In-Reply-To: <20070819182658.GC25214@uio.no>

* 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