| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | 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:00:19 |
| Message-ID: | 20140424170018.GZ25695@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
This would make uuidserial not quite as simple as SERIAL pseudotype, of
course.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-04-24 17:02:35 | Re: 9.4 Proposal: Initdb creates a single table |
| Previous Message | Tom Lane | 2014-04-24 16:53:11 | Re: 9.4 Proposal: Initdb creates a single table |