Re: pervasiveness of surrogate (also called synthetic) keys

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Rob Sargent <robjsargent(at)gmail(dot)com>
Cc: Greg Smith <greg(at)2ndQuadrant(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: pervasiveness of surrogate (also called synthetic) keys
Date: 2011-05-03 05:04:22
Message-ID: 4DBF8CD6.5040307@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 03/05/11 12:57, Rob Sargent wrote:

> Hm.. Virtual machines as assets. Mortgage backed securities, anyone.

Well, sure ... but the software running on them is tracked as part of
licensing compliance efforts, whether or not the virtual hardware its
self is an "asset" its self. The DB designer chose to use the host's MAC
address to identify the host, and the tracking software can't tell the
difference between a VM and a physical host.

The other problem with that is that it doesn't deal well with
multi-homed hosts. All in all, it's just a dumb design, and was fixed a
while ago, but it's an illustration of how something that seems like an
obvious natural key doesn't always stay one.

--
Craig Ringer

In response to

Browse pgsql-general by date

  From Date Subject
Next Message alan bryan 2011-05-03 05:12:06 Seg Fault in backend after beginning to use xpath (PG 9.0, FreeBSD 8.1)
Previous Message Rob Sargent 2011-05-03 04:57:29 Re: pervasiveness of surrogate (also called synthetic) keys