Database denormalization

From: JG <vhz95(at)rocketmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Database denormalization
Date: 2012-02-13 13:48:40
Message-ID: 1329140920.82701.YahooMailNeo@web122611.mail.ne1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi

I would like to ask weather PostgreSQL does database denormalization at runtime.

That is, for example, if I have a normalized database and I use lots of querys that would run faster on a denormalized database, than will PostgreSQL create a denormalized version of the database for internal use.

To specify further, the question is, can I count on PostgreSQL to denormalize the database when it would be better for the performance, or should I always denormalize the database and all the querys myself.

I have looked for answers on the subject, but all I managed to find was a wiki article at http://en.wikipedia.org/wiki/Denormalization that says:

"The preferred method is to keep the logical design normalised, but allow the database management system (DBMS) to store additional redundant information on disk to optimise query response. In this case it is the DBMS software's responsibility to ensure that any redundant copies are kept consistent. This method is often implemented in SQL as indexed views (Microsoft SQL Server) or materialised views (Oracle)."

So in the case of PostgreSQL, do I also have to use views or are there some other ways?

Thanks

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Wim Bertels 2012-02-13 13:50:12 Re: psql latex and newlines
Previous Message Albe Laurenz 2012-02-13 08:56:55 Re: 9.1.1 crash