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

Re: [GENERAL] UUID's as primary keys

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Thomas Hallgren <thomas(at)tada(dot)se>, Psql_General <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] UUID's as primary keys
Date: 2006-06-29 03:23:17
Message-ID: 9961.1151551397@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Greg Stark <gsstark(at)mit(dot)edu> writes:
> Hm, so it could be stored on disk without the length header as long as
> the length header is added to the in-memory representation? I don't
> think the type system has hooks for reading and storing data to disk
> though.

No, it doesn't, and we'd pay a nonzero price for allowing that.
Currently the executor doesn't have to care (much) about whether a
tuple is on-disk or in-memory --- the individual datums look the same
either way.  Allowing them to be different would force a lot of
format conversion steps that currently need not happen.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: markDate: 2006-06-29 06:02:32
Subject: Re: Fixed length datatypes. WAS [GENERAL] UUID's as
Previous:From: Greg StarkDate: 2006-06-29 00:43:23
Subject: Re: optimizing constant quals within outer joins

pgsql-general by date

Next:From: markDate: 2006-06-29 06:02:32
Subject: Re: Fixed length datatypes. WAS [GENERAL] UUID's as
Previous:From: Greg StarkDate: 2006-06-29 00:34:11
Subject: Re: [GENERAL] UUID's as primary keys

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