Re: Identity column data type difference in PostgreSQL and Oracle - Mailing list pgsql-general

From Muhammad Ikram
Subject Re: Identity column data type difference in PostgreSQL and Oracle
Date
Msg-id CAGeimVqcPM3m_CBxQSnvGpY5r7ZEcE1RJXXTVriu8Ga_wc8XSw@mail.gmail.com
Whole thread Raw
In response to Re: Identity column data type difference in PostgreSQL and Oracle  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-general
Thanks for the advice.


On Fri, 3 May 2024 at 16:09, Peter Eisentraut <peter@eisentraut.org> wrote:
On 03.05.24 12:57, Muhammad Ikram wrote:
> Tables which have an identity column in Oracle when migrated to
> PostgreSQL, the data type of Identity column is changed to bigint from
> number by the tools. This causes the size of column to be reduced to max
> value supported by bigint which is way lower than the oracle  number max.

Sequences in PostgreSQL are limited to bigint, there is nothing that can
be changed about that.  But you are approximately the first person to
complain that the range of ids provided by bigint is too small, so maybe
it's worth reconsidering whether it would work for you.  If it really is
too small, maybe a uuid would work.  But yes, you'll need to make some
adjustments to the rest of your database or application code if you make
such changes.

pgsql-general by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Identity column data type difference in PostgreSQL and Oracle
Next
From: Iman Bakhtiari
Date:
Subject: I have ansible for postgres-etcd-patroni