Feedback-ID: ie0a040ee:Fastmail
Message-ID: <17582807-412b-406e-9504-f0e1089888a1@eisentraut.org>
Date: Fri, 3 May 2024 13:09:41 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Identity column data type difference in PostgreSQL and Oracle
To: Muhammad Ikram <mmikram@gmail.com>,
 PostgreSQL General <pgsql-general@lists.postgresql.org>
References: <CAGeimVpSjtMuq_J8bL_U3qe4ZaH78sVc35sdjZWO9sqJyLtLnA@mail.gmail.com>
Content-Language: en-US
From: Peter Eisentraut <peter@eisentraut.org>
In-Reply-To: <CAGeimVpSjtMuq_J8bL_U3qe4ZaH78sVc35sdjZWO9sqJyLtLnA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/17582807-412b-406e-9504-f0e1089888a1%40eisentraut.org>
Precedence: bulk

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.