Re: Indexes on UUID - Fragmentation Issue

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: uday(dot)bhaskar579(at)gmail(dot)com
Cc: postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Indexes on UUID - Fragmentation Issue
Date: 2018-10-29 14:28:44
Message-ID: CAHyXU0x3vevK4ss+=XY5rvnByTx93TiCBK7K1ghoeeA-msC0UQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, Oct 29, 2018 at 9:18 AM Uday Bhaskar V
<uday(dot)bhaskar579(at)gmail(dot)com> wrote:
>
> Hi,
>
> I have searched in many postgres blogs for Sequential UUID generation, which can avoid Fragmentation issue.
>
> I did a POC(in postgres) with sequential UUID against Non sequential which has shown lot of different in space utilization and index size. Sql server has "newsequentialid" which generates sequential UUID. I have created C function which can generate a sequential UUID, but I am not sure how best I can use that in postgres.
>
> I would really like to contribute to Postgres, If I can. Please let me know your thoughts or plans regarding UUID generation.

I think the right approach here is to build a custom extension. There
are lots of examples of extensions within contrib and on pgxn.
https://pgxn.org/ I guess there might be some utility for this type
as UUID fragmetnation is a major problem (it's one of the reasons I
discourage the use off UUID type indexes).

merlin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andreas Karlsson 2018-10-29 14:52:21 Re: Indexes on UUID - Fragmentation Issue
Previous Message Uday Bhaskar V 2018-10-29 13:29:40 Indexes on UUID - Fragmentation Issue