Skip site navigation (1) Skip section navigation (2)

Sparse Data

From: "Walker, Jed S" <Jed_Walker(at)cable(dot)comcast(dot)com>
To: <pgsql-novice(at)postgresql(dot)org>
Subject: Sparse Data
Date: 2005-05-24 15:57:58
Message-ID: 4A59B6AA01F1874283EA66C976ED51FC0E199C@COENGEXCMB01.cable.comcast.com (view raw or flat)
Thread:
Lists: pgsql-novice
Does sparse data cause significant space wastage or performance issues
in PostgreSQL?

We are building an application that stores assets. Each different type
of asset has different attributes and in initial design we decided to
store each attribute in separate tables to avoid having a lot of sparse
data. It turns out, after many revisions and working throught the asset
definitions, that are more similar than we thought, but still not very
alike. This is making me rethink splitting them out into separate
tables.

Given that PostgreSQL writes new blocks when a block changes (instead of
updating the block), it made me wonder if sparse data is really an issue
in PostgreSQL (because if it always writes a new block to replace a
block that has changed, then it wouldn't have to waste any or much
space).

Any input or knowledge would be great,

Thanks,


Jed S. Walker




Responses

pgsql-novice by date

Next:From: Miguel que te importaDate: 2005-05-24 16:08:25
Subject: Re: Trigger unhappy (Correction)
Previous:From: peter nkosiDate: 2005-05-24 15:13:10
Subject: INVESTMENT

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group