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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Surrogate keys (Was: enums)


  • From: Leandro GuimarÃes Faria Corcete DUTRA <leandro(at)dutra(dot)fastmail(dot)fm>
  • To: pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: Surrogate keys (Was: enums)
  • Date: Wed, 18 Jan 2006 13:08:53 +0000 (UTC)
  • Message-id: <loom.20060118T140650-865@post.gmane.org> <text/plain>

Jim C. Nasby <jnasby <at> pervasive.com> writes:

> a) the optimizer does a really poor job on multi-column index statistics

So it should be fixed?

And there are a *lot* of singular, natural keys.


> b) If each parent record will have many children, the space savings from
> using a surrogate key can be quite large

Not such a common case.


> c) depending on how you view things, putting actual keys all over the
> place is denormalized

How come?  Never!


> Generally, I just use surrogate keys for everything unless performance
> dictates something else.

What I am proposing is the reverse: use natural keys for everything unless 
performance dictates something else.

In support of my PoV: 
http://blogs.ittoolbox.com/database/soup/archives/007327.asp?rss=1





Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group