Re: Indexes on UUID - Fragmentation Issue - Mailing list pgsql-performance

From Uday Bhaskar V
Subject Re: Indexes on UUID - Fragmentation Issue
Date
Msg-id CAFowjW1xV9EE4sDNOBE5Qgvuc4iN1Jttn1F0kBsO7J3QYEcJsQ@mail.gmail.com
Whole thread Raw
In response to Re: Indexes on UUID - Fragmentation Issue  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-performance
We have migrated our Database from Oracle to Postgresql there because of replication we went for UUIDs. I have C function ready, will try.
Thanks,
Uday

On Mon, Oct 29, 2018 at 7:58 PM Merlin Moncure <mmoncure@gmail.com> wrote:
On Mon, Oct 29, 2018 at 9:18 AM Uday Bhaskar V
<uday.bhaskar579@gmail.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

pgsql-performance by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: Indexes on UUID - Fragmentation Issue
Next
From: MichaelDBA
Date:
Subject: Re: Indexes on UUID - Fragmentation Issue