| From: | <kaiq(at)realtyideas(dot)com> |
|---|---|
| To: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
| Cc: | sevo(at)ip23(dot)net, davidb(at)vectormath(dot)com, pgsql-general(at)postgreSQL(dot)org |
| Subject: | Re: [GENERAL] using ID as a key |
| Date: | 2000-02-07 17:30:37 |
| Message-ID: | Pine.LNX.4.10.10002071127300.12245-100000@picasso.realtyideas.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 7 Feb 2000, Ed Loehr wrote:
> These are resolvable problems. One way to do a programmatic ID
> generation as David B. suggests is to have a DB server whose purpose
> is to issue "seed numbers" which designate, through use of a
> pre-determined multiplier, a *range* of allocated IDs guaranteed to be
> unique across all seed requesters. This avoids both of the problems
> raised above (throughput and synchronization).
.....
> not time-ordered. A few more details must be handled, and there is
> some maintainance overhead, but it seems to work fairly well.
sounds familiar -- the seed server can be pg, and other servers can be
user-program, and pg's sequence can do this already.
and, it seems not "programmatically at all.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marten Feldtmann | 2000-02-07 18:01:29 | Re: [GENERAL] using ID as a key |
| Previous Message | Marten Feldtmann | 2000-02-07 17:17:41 | Re: [GENERAL] using ID as a key |