RE: Disk space consumption: character varying(255) versus text used for index

Just to make it a little more clear, PostgreSQL has a binary UUID type that should house your GUID’s perfectly efficiently. (It also provides a lot of other useful functionality and speed improvements):

https://www.postgresql.org/docs/12/datatype-uuid.html

From: Justin <zzzzz(dot)graf(at)gmail(dot)com>
Sent: Friday, December 20, 2019 12:06 PM
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: ruff(at)netwake(dot)com; pgsql-novice(at)postgresql(dot)org
Subject: Re: Disk space consumption: character varying(255) versus text used for index

Have question this states the GUID is the text Hex value form a UUID if so that 36bytes long vs integer that is 128bits if that is the case convert this GUID to UUID type

or am i missing something?

On Fri, Dec 20, 2019 at 1:55 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us<mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
Marcel Ruff <ruff(at)netwake(dot)com<mailto:ruff(at)netwake(dot)com>> writes:
> my btree index for
> guid | character varying(255)
> is currently 6.9GB (almost all guid entries are of size 37bytes)
> If I would change the data type to
> guid | text
> would the index size be reduced (without hitting performance)?

Wouldn't make any difference at all.

regards, tom lane