From: | mark(at)mark(dot)mielke(dot)cc |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, nathan wagner <nw(at)hydaspes(dot)if(dot)org> |
Subject: | Re: uuid type for postgres |
Date: | 2005-09-06 22:06:48 |
Message-ID: | 20050906220648.GD3069@mark.mielke.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
On Tue, Sep 06, 2005 at 05:54:34PM -0400, Tom Lane wrote:
> I don't see any "big opposition". People are simply questioning the
> idea whether it belongs in core PG. The reason we don't want to accept
> everything-and-the-kitchen-sink in core is that we have only limited
> manpower to maintain it. So you've got to justify that we should spend
> our effort here and not elsewhere. There's a fair amount of nearly
> ...
> been there awhile. So one of the questions that's going to be asked is
> how useful/popular it's really going to be.
Sounds reasonable, and certainly no more than I expected. If Nathan
hadn't raised the issue, it probably would have been a few months
before I raised it myself.
> One thing that is raising my own level of concern quite a bit is the
> apparent portability issues. Code that isn't completely portable is a
> huge maintainability problem; in particular, stuff that requires
> system-dependent behavior used nowhere else in Postgres is a real pain.
> It sounds like the UUID code expects to be able to get at the machine's
> MAC address, which suggests serious issues in (a) relying on
> not-too-standard APIs, (b) possible protection issues (will an
> unprivileged process be able to get at the MAC address?), and (c)
> ill-defined behavior on machines with more or less than one MAC address.
> Not to mention that MAC addresses aren't so unique as all that.
I'll try to prepare an answer for this. (I started to write a lot of
information - but is it unverified from memory, and perhaps should be
more authoritative before presented as truth)
> The bottom line is that we're willing to listen, but it's not by any
> means a slam dunk to get this into the distribution.
Sounds good.
Cheers,
mark
--
mark(at)mielke(dot)cc / markm(at)ncf(dot)ca / markm(at)nortel(dot)com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
From | Date | Subject | |
---|---|---|---|
Next Message | nathan wagner | 2005-09-06 22:22:41 | Re: uuid type for postgres |
Previous Message | Tom Lane | 2005-09-06 22:02:27 | Re: Remove xmin and cmin from frozen tuples |
From | Date | Subject | |
---|---|---|---|
Next Message | nathan wagner | 2005-09-06 22:40:36 | Re: uuid type for postgres |
Previous Message | Tom Lane | 2005-09-06 21:54:34 | Re: uuid type for postgres |