Re: Identity column data type difference in PostgreSQL and Oracle

From: Muhammad Ikram <mmikram(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Identity column data type difference in PostgreSQL and Oracle
Date: 2024-05-03 11:11:27
Message-ID: CAGeimVqcPM3m_CBxQSnvGpY5r7ZEcE1RJXXTVriu8Ga_wc8XSw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks for the advice.

On Fri, 3 May 2024 at 16:09, Peter Eisentraut <peter(at)eisentraut(dot)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.
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Iman Bakhtiari 2024-05-03 12:11:36 I have ansible for postgres-etcd-patroni
Previous Message Peter Eisentraut 2024-05-03 11:09:41 Re: Identity column data type difference in PostgreSQL and Oracle