MIME-Version: 1.0
References: <CAGeimVpSjtMuq_J8bL_U3qe4ZaH78sVc35sdjZWO9sqJyLtLnA@mail.gmail.com>
 <17582807-412b-406e-9504-f0e1089888a1@eisentraut.org>
In-Reply-To: <17582807-412b-406e-9504-f0e1089888a1@eisentraut.org>
From: Muhammad Ikram <mmikram@gmail.com>
Date: Fri, 3 May 2024 16:11:27 +0500
Message-ID: <CAGeimVqcPM3m_CBxQSnvGpY5r7ZEcE1RJXXTVriu8Ga_wc8XSw@mail.gmail.com>
Subject: Re: Identity column data type difference in PostgreSQL and Oracle
To: Peter Eisentraut <peter@eisentraut.org>
Cc: PostgreSQL General <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000009bcf7106178ac8a5"
Archived-At: <https://www.postgresql.org/message-id/CAGeimVqcPM3m_CBxQSnvGpY5r7ZEcE1RJXXTVriu8Ga_wc8XSw%40mail.gmail.com>
Precedence: bulk

--0000000000009bcf7106178ac8a5
Content-Type: text/plain; charset="UTF-8"

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.
>
>

--0000000000009bcf7106178ac8a5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div>Thanks for the advice.</div><div><br></div><div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, 3 May 2024 at 16:09,=
 Peter Eisentraut &lt;<a href=3D"mailto:peter@eisentraut.org">peter@eisentr=
aut.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 03.05.24 =
12:57, Muhammad Ikram wrote:<br>
&gt; Tables which have an identity column in Oracle when migrated to <br>
&gt; PostgreSQL, the data type of Identity column is changed to bigint from=
 <br>
&gt; number by the tools. This causes the size of column=C2=A0to be reduced=
 to max <br>
&gt; value supported by bigint which is way lower than the oracle=C2=A0 num=
ber max.<br>
<br>
Sequences in PostgreSQL are limited to bigint, there is nothing that can <b=
r>
be changed about that.=C2=A0 But you are approximately the first person to =
<br>
complain that the range of ids provided by bigint is too small, so maybe <b=
r>
it&#39;s worth reconsidering whether it would work for you.=C2=A0 If it rea=
lly is <br>
too small, maybe a uuid would work.=C2=A0 But yes, you&#39;ll need to make =
some <br>
adjustments to the rest of your database or application code if you make <b=
r>
such changes.<br>
<br>
</blockquote></div></div>

--0000000000009bcf7106178ac8a5--