| From: | Yann Michel <yann-postgresql(at)spline(dot)de> |
|---|---|
| To: | Rod Taylor <pg(at)rbt(dot)ca> |
| Cc: | pg(at)fastcrypt(dot)com, Frank Wiles <frank(at)wiles(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Postgresql Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Low Performance for big hospital server .. |
| Date: | 2005-01-06 19:09:57 |
| Message-ID: | 20050106190957.GA15890@zong.spline.inf.fu-berlin.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi
On Thu, Jan 06, 2005 at 12:51:14PM -0500, Rod Taylor wrote:
> On Thu, 2005-01-06 at 12:35 -0500, Dave Cramer wrote:
> > Reading can be worse for a normalized db, which is likely what the
> > developers were concerned about.
>
> To a point. Once you have enough data that you start running out of
> space in memory then normalization starts to rapidly gain ground again
> because it's often smaller in size and won't hit the disk as much.
Well, in datawarehousing applications you'll often denormalize your
entities due to most of the time the access method is a (more or less)
simple select.
Regards,
Yann
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Randolf Richardson | 2005-01-06 19:14:45 | Re: Some Performance Advice Needed |
| Previous Message | Randolf Richardson | 2005-01-06 19:01:38 | PostgreSQL vs. Oracle vs. Microsoft |