Re: Issues with upserts

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: André Hänsel <andre(at)webkr(dot)de>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Issues with upserts
Date: 2022-07-13 15:13:43
Message-ID: d03e21be-5c88-0085-e485-405d09a60727@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 7/13/22 07:58, André Hänsel wrote:
> Jeremy Smith wrote:

> CREATE TABLE t (
>
>     id serial PRIMARY KEY,
>
>     name text NOT NULL UNIQUE,
>
>     address text NOT NULL
>
> );

>
> This will yield “8”, showing that new sequence numbers have been
> generated for each attempt.
>

If running out of id's is a concern use bigserial instead of serial as
it uses bigint:

bigint -9223372036854775808 to +9223372036854775807

vs

integer for serial:

integer -2147483648 to +2147483647

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bryn Llewellyn 2022-07-13 23:33:53 Re: Seems to be impossible to set a NULL search_path
Previous Message David G. Johnston 2022-07-13 15:06:46 Re: Issues with upserts