Re: Switching Primary Keys to BigInt - Mailing list pgsql-general

From Mohamed Wael Khobalatte
Subject Re: Switching Primary Keys to BigInt
Date
Msg-id CABZeWdwsaMvjU7ECLKpAr5WZVp+5LS7NAcqhzg1KHkFHQQr1xQ@mail.gmail.com
Whole thread Raw
In response to Re: Switching Primary Keys to BigInt  (Michael Lewis <mlewis@entrata.com>)
Responses Re: Switching Primary Keys to BigInt
Re: Switching Primary Keys to BigInt
List pgsql-general
>  > test_(aklaver)5432> alter table change_seq alter COLUMN id set data type
> bigint;
> ALTER TABLE
> test_(aklaver)5432> \d change_seq
>                              Table "public.change_seq"
>   Column |  Type  | Collation | Nullable |                Default
> --------+--------+-----------+----------+----------------------------------------
>
>   id     | bigint |           | not null |
> nextval('change_seq_id_seq'::regclass)
> Indexes:
>      "change_seq_pkey" PRIMARY KEY, btree (id)

This is significant downtime, since it locks exclusively, no? We want to avoid that.

> Side note- EOL for 9.6 is coming next year so just a plug for upgrading when possible, perhaps utilizing pglogical to get to v11 or 12.

Yep, we are painfully aware. The id growth will beat us to it, so we need to deal with that first. 


pgsql-general by date:

Previous
From: Michael Lewis
Date:
Subject: Re: Switching Primary Keys to BigInt
Next
From: Michał Lis
Date:
Subject: Problem with pg_service.conf