From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Rafal Pietrak <rafal(at)ztk-rp(dot)eu> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: looking for a globally unique row ID |
Date: | 2017-09-14 22:40:01 |
Message-ID: | fbe3daa0-c917-ccea-7991-4b894a181d2e@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 09/14/2017 03:27 PM, David G. Johnston wrote:
> On Thu, Sep 14, 2017 at 12:45 AM, Rafal Pietrak <rafal(at)ztk-rp(dot)eu
> <mailto:rafal(at)ztk-rp(dot)eu>>wrote:
>
> Hello everybody,
>
> Can anybody help me find a way to implement an ID which:
>
> 1. guarantees being unique across multiple tables.
>
> 2. guarantees its uniqueness not only during INSERT, but also during the
> lifetime of the database/application (e.i. during future UPDATES).
>
> 3. guarantees persistence of value across database
> backup/restore/upgrade.
>
> an obvious candidate - a single SERIAL() (same serial) used in every
> table that needs that ID does not guarantee (2).
Isn't this what GUIDS are for?
JD
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.us
***** Unless otherwise stated, opinions are my own. *****
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2017-09-15 02:36:51 | Re: BDR, near xid wraparound, a lot of files in pg_subtrans directory |
Previous Message | David G. Johnston | 2017-09-14 22:27:00 | Re: looking for a globally unique row ID |