pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steve Atkins <steve@blighty.com>
To: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Using PK value as a String
Date: Tue, 12 Aug 2008 08:36:10 -0700
Message-ID: <233F1248-E3EA-4572-9310-4E4BC13995DE@blighty.com> (raw)
In-Reply-To: <20080812112136.72af4bff.wmoran@collaborativefusion.com>
References: <18986.60888.qm@web25807.mail.ukl.yahoo.com>
	<48A15ECF.5030203@sime.com>
	<87od3ywg4n.fsf@oxford.xeocode.com>
	<0673579A-B049-4619-B6E4-EE427FB0DDBA@globalinn.com>
	<1343069D-263F-4D99-BF7E-269C8F0E7F1F@houseofdesign.de>
	<20080812110416.8e0d6e1c.wmoran@collaborativefusion.com>
	<4D558373-E7B0-40EC-95EF-FDFE7046ABA2@houseofdesign.de>
	<20080812112136.72af4bff.wmoran@collaborativefusion.com>


On Aug 12, 2008, at 8:21 AM, Bill Moran wrote:

> In response to Moritz Onken <onken@houseofdesign.de>:
>
>>
>> Am 12.08.2008 um 17:04 schrieb Bill Moran:
>>
>>> In response to Moritz Onken <onken@houseofdesign.de>:
>>>
>>>> We chose UUID as PK because there is still some information in an
>>>> integer key.
>>>> You can see if a user has registered before someone else  
>>>> (user1.id <
>>>> user2.id)
>>>> or you can see how many new users registered in a specific period  
>>>> of
>>>> time
>>>> (compare the id of the newest user to the id a week ago). This is
>>>> information
>>>> which is in some cases critical.
>>>
>>> So you're accidentally storing critical information in magic values
>>> instead of storing it explicitly?
>>>
>>> Good luck with that.
>>
>> How do I store critical information? I was just saying that it easy
>> to get some information out of a primary key which is an incrementing
>> integer. And it makes sense, in some rare cases, to have a PK which
>> is some kind of random like UUIDs where you cannot guess the next  
>> value.
>
> I just repeated your words.  Read above "this is information which  
> is in
> some cases critical."
>
> If I misunderstood, then I misunderstood.
>

I think Moritz is more concerned about leakage of critical information,
rather than intentional storage of it. When a simple incrementing  
integer
is used as an identifier in publicly visible places (webapps, ticketing
systems) then that may leak more information than intended.

Cheers,
   Steve




view thread (23+ messages)  latest in thread

Message-ID: <233F1248-E3EA-4572-9310-4E4BC13995DE@blighty.com>
Permalink:  ../233F1248-E3EA-4572-9310-4E4BC13995DE@blighty.com/
Also on:    postgresql.org/message-id/233F1248-E3EA-4572-9310-4E4BC13995DE@blighty.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: steve@blighty.com
  Subject: Re: Using PK value as a String
  In-Reply-To: <233F1248-E3EA-4572-9310-4E4BC13995DE@blighty.com>
  References: <18986.60888.qm@web25807.mail.ukl.yahoo.com> <48A15ECF.5030203@sime.com> <87od3ywg4n.fsf@oxford.xeocode.com> <0673579A-B049-4619-B6E4-EE427FB0DDBA@globalinn.com> <1343069D-263F-4D99-BF7E-269C8F0E7F1F@houseofdesign.de> <20080812110416.8e0d6e1c.wmoran@collaborativefusion.com> <4D558373-E7B0-40EC-95EF-FDFE7046ABA2@houseofdesign.de> <20080812112136.72af4bff.wmoran@collaborativefusion.com> <233F1248-E3EA-4572-9310-4E4BC13995DE@blighty.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox