From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Uday Bhaskar V <uday(dot)bhaskar579(at)gmail(dot)com>, sehrope(at)jackdb(dot)com |
Cc: | adambrusselback(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Sequential UUID Generation |
Date: | 2018-11-27 16:51:43 |
Message-ID: | 1a4e6c4b-93c9-4d6b-2e5c-91e4de9a5207@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/19/18 2:08 PM, Uday Bhaskar V wrote:
> I tried below function as which can be used as default to column. But
> every time we need to created 2 sequences, 1st one takes care of the
> first 8 bytes and 2nd takes care of the 2nd part of the UUID. I have not
> tested index and space utilization. I have to examine this. This might
> not be completely unique in the nature. but still trying for the best.
>
I got a bit bored a couple of days ago, so I wrote an extension
generating UUIDs based on either a sequence or timestamp. See
https://blog.2ndquadrant.com/sequential-uuid-generators/
for an explanation and some simple test results.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2018-11-27 17:11:38 | Re: Continue work on changes to recovery.conf API |
Previous Message | Andres Freund | 2018-11-27 16:43:32 | Re: Continue work on changes to recovery.conf API |