Home > mailing lists

Advice on Contiguous IDs - Mailing list pgsql-docs

From	Brian McKiernan
Subject	Advice on Contiguous IDs
Date	January 9, 2018 15:06:26
Msg-id	5a546fcab6ae2e0000bdb8e4@polymail.io Whole thread Raw
Responses	Re: Advice on Contiguous IDs (Alvaro Herrera <alvherre@alvh.no-ip.org>) Re: Advice on Contiguous IDs ("David G. Johnston" <david.g.johnston@gmail.com>) Re: Advice on Contiguous IDs (Steve Atkins <steve@blighty.com>) Re: Advice on Contiguous IDs (Vik Fearing <vik.fearing@2ndquadrant.com>)
List	pgsql-docs

Tree view

Hi Folks,

Looking for some help/advice - not sure if this is the appropriate channel.

My Issue:

My primary keys in a certain table are not contiguous.

What I have done so far:

I have checked the documentation and found: https://wiki.postgresql.org/wiki/FAQ#Why_are_there_gaps_in_the_numbering_of_my_sequence.2FSERIAL_column.3F_Why_aren.27t_my_sequence_nu

mbers_reused_on_transaction_abort.3F

My Question:

1) What event would cause the CACHE clause in CREATE SEQUENCE to make an out of sequence next number?

2) In all cases am I correct in my thinking that in order to create contiguous primary key IDs then performance will greatly suffer? Do we have an idea of how bad this will generally be or what does that depend upon?

Many thanks in advance,

Brian

pgsql-docs by date:

From: Simon Riggs
Date: 07 January 2018, 00:15:15
Subject: Re: Is this still accurate?

From: PG Doc comments form
Date: 09 January 2018, 19:05:42
Subject: Describe UNION's cast on derived table

Advice on Contiguous IDs - Mailing list pgsql-docs

Previous

Next