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

Fixed length datatypes. WAS [GENERAL] UUID's as primary keys

From: Thomas Hallgren <thomas(at)tada(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Fixed length datatypes. WAS [GENERAL] UUID's as primary keys
Date: 2006-06-28 16:39:16
Message-ID: 44A2B0B4.3040600@tada.se (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Martijn van Oosterhout wrote:
> On Wed, Jun 28, 2006 at 01:56:47PM +0200, Thomas Hallgren wrote:
>> A user that is trusted with installing a C-function in the backend is 
>> free to scan the process memory anyway so in what way did that increase 
>> the security? IMHO, the only relevant security in that context is to 
>> have trusted people install trusted modules. I'm surprised that 
>> something like that made you remove significant functionality.
> 
> You're missing the point. The type output function is not generally a
> priveledged function. Think bpcharout, text_out, numeric_out, etc...
> These can be called by users directly and the input to those functions
> cannot be trusted.
> 
Ah, OK that makes sense. An alternative solution when the signature was changed could 
perhaps have been to pass one single argument, a structure appointing the data and its 
associated type. My idea would work if the data and its type lived together always from the 
moment its instantiated (read from disk or otherwise) and until death do them apart (or the 
data is stored on disk, in which case the tupledesc knows what it is). I guess that would 
imply a major rewrite and that my desire to have a RAW fixed length type isn't enough 
motivation to do that :-)

Instead, I would like to humbly request the inclusion of a UUID datatype (or an opaque 128 
bit datatype) in the core package. It's increasingly common and some databases (MS 
SQLServer) already have built in support for it.

Regards,
Thomas Hallgren


In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2006-06-28 17:04:16
Subject: Re: Instability in TRUNCATE regression test
Previous:From: Marc MunroDate: 2006-06-28 16:28:14
Subject: Index corruption

pgsql-general by date

Next:From: Jim C. NasbyDate: 2006-06-28 17:10:53
Subject: Re: Fixed length datatypes. WAS [GENERAL] UUID's as primary keys
Previous:From: Leif B. KristensenDate: 2006-06-28 16:25:22
Subject: Re: empty text fields

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group