| From: | Justin <zzzzz(dot)graf(at)gmail(dot)com> |
|---|---|
| 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 |
| Date: | 2019-12-20 19:06:17 |
| Message-ID: | CALL-XeOFZ0sFuYFk-KLBhBu8DmArFkkKvPRXFwE5GisN04GBMA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
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> wrote:
> Marcel Ruff <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
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Froehlich | 2019-12-21 14:41:13 | RE: Disk space consumption: character varying(255) versus text used for index |
| Previous Message | Tom Lane | 2019-12-20 18:55:44 | Re: Disk space consumption: character varying(255) versus text used for index |