Gevik Babakhani wrote:
- new_guid() function is supported. This function is based on V4 random
uuid value. It generated 16 random bytes with uuid 'variant' and
'version'. It is not guaranteed to produce unique values
Isn't guaranteed uniqueness the very attribute that's expected? AFAIK
Andreas Pflug [EMAIL PROTECTED] writes:
Isn't guaranteed uniqueness the very attribute that's expected? AFAIK
there's a commonly accepted algorithm providing this.
Anyone who thinks UUIDs are guaranteed unique has been drinking too much
of the kool-aid. They're at best probably unique. Some
Completely agreed. I can remove the function from the patch. The
temptation was just too high not to include the new_guid() in the
patch :)
On Mon, 2006-09-18 at 10:33 -0400, Tom Lane wrote:
Andreas Pflug [EMAIL PROTECTED] writes:
Isn't guaranteed uniqueness the very attribute that's
On Mon, Sep 18, 2006 at 10:33:22AM -0400, Tom Lane wrote:
Andreas Pflug [EMAIL PROTECTED] writes:
Isn't guaranteed uniqueness the very attribute that's expected? AFAIK
there's a commonly accepted algorithm providing this.
Anyone who thinks UUIDs are guaranteed unique has been drinking too
Hi,
This is cosmetic patch that puts the parameters in the correct order (same
as other similar commands).
--
Euler Taveira de Oliveira
http://www.timbira.com/
x
Description: Binary data
---(end of broadcast)---
TIP 5: don't forget to
On Mon, 2006-09-18 at 13:33 -0500, Euler Taveira de Oliveira wrote:
This is cosmetic patch that puts the parameters in the correct order (same
as other similar commands).
Applied, thanks.
-Neil
---(end of broadcast)---
TIP 1: if
If you're going to yank it, please at least include a generator in
contrib.
Personally, I'd like to see at least some kind of generator in core,
with appropriate info/disclaimers in the docs. A simple random-number
generator is probably the best way to go in that regard. I think that
most people
On Mon, Sep 18, 2006 at 04:00:22PM -0500, Jim C. Nasby wrote:
BTW, at a former company we used SHA1s to identify files that had been
uploaded. We were wondering on the odds of 2 different files hashing to
the same value and found some statistical comparisons of probabilities.
I don't recall
On Mon, Sep 18, 2006 at 12:23:16PM -0400, [EMAIL PROTECTED] wrote:
I have UUID generation in core in my current implementation. In the
last year that I've been using it, I have already chosen twice to
generate UUIDs from my calling program. I find it faster, as it avoids
have to call out to
On Mon, 2006-09-18 at 16:00 -0500, Jim C. Nasby wrote:
BTW, at a former company we used SHA1s to identify files that had been
uploaded. We were wondering on the odds of 2 different files hashing to
the same value and found some statistical comparisons of probabilities.
I don't recall the
If you have trouble with duplicate OIDs
Please use patch-0.2 for testing. I have changed the OIDs to 5000 range.
You can download it from:
http://www.truesoftware.net/pgsql/uuid/patch-0.2/
On Mon, 2006-09-18 at 01:00 +0200, Gevik Babakhani wrote:
Folks,
The following patch implements the
On Mon, 18 Sep 2006, Jie Zhang wrote:
Hi all,
It seems that my previous email to pgsql-hackers about the latest bitmap
index patch did not go through. Please find the latest patch in the
attachment. Any suggestions and comments are appreciated.
This patch is generated against the
On Mon, Sep 18, 2006 at 04:17:50PM -0500, Jim C. Nasby wrote:
On Mon, Sep 18, 2006 at 12:23:16PM -0400, [EMAIL PROTECTED] wrote:
I have UUID generation in core in my current implementation. In the
last year that I've been using it, I have already chosen twice to
generate UUIDs from my
13 matches
Mail list logo
