| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Hannu Krosing <hannu(at)2ndQuadrant(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 9.4 Proposal: Initdb creates a single table |
| Date: | 2014-04-24 17:02:35 |
| Message-ID: | 535943AB.9030207@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04/24/2014 08:00 PM, Alvaro Herrera wrote:
> Tom Lane wrote:
>
>> This is not our fault, and I don't want us to get caught up in trying
>> to fix a fundamentally broken concept --- which is what a generic
>> "uuidserial" API would be. If you try to paper over the difficulties
>> here, they'll just bite you on the rear someday.
>
> But we have non-colliding generation technology for OIDs in system
> catalogs. We could try to reuse the idea in a UUID generator: grab one
> value, try to insert; if it fails generate a new one, lather, rinse,
> repeat.
Umm, UUID stands for Universally Unique IDentifier. That would hardly be
*universally* unique.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-04-24 17:07:07 | Re: 9.4 Proposal: Initdb creates a single table |
| Previous Message | Alvaro Herrera | 2014-04-24 17:00:19 | Re: 9.4 Proposal: Initdb creates a single table |