| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Brian McKiernan <brian(dot)mckiernan(at)firstcircle(dot)com> |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Advice on Contiguous IDs |
| Date: | 2018-01-09 16:47:35 |
| Message-ID: | 20180109164735.ic7pmtxehekv7paf@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Brian McKiernan wrote:
> My Issue:
> My primary keys in a certain table are not contiguous.
If you have a need to have values that are contiguous, you need to ask
yourself why and then see what mechanism provides the semantics you
need. An easy way is to lock the table containing the column, for
example, which of course means only one transaction can do it at a time.
For many use cases this is good enough.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2018-01-09 16:53:57 | Re: libpq options |
| Previous Message | PG Doc comments form | 2018-01-09 13:05:42 | Describe UNION's cast on derived table |