From: | "Godfrin, Philippe E" <Philippe(dot)Godfrin(at)nov(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | RE: [EXTERNAL] Re: Numeric data types |
Date: | 2020-08-31 17:32:23 |
Message-ID: | SA0PR15MB39330E3775F7EB235276151382510@SA0PR15MB3933.namprd15.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks Bruce, I suppose you mean n32 -> n64 OK, but n64->n32 chance of 32-bit overflow...
pg
From: Bruce Momjian <bruce(at)momjian(dot)us>
Sent: Monday, August 31, 2020 11:54 AM
To: Godfrin, Philippe E <Philippe(dot)Godfrin(at)nov(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: [EXTERNAL] Re: Numeric data types
On Mon, Aug 31, 2020 at 04:38:05PM +0000, Godfrin, Philippe E wrote:
> Greetings Listees (frist time poster!)
>
>
>
> Considering the difference between 64 bit and 32 bit numeric datatypes. We have
> source databases that are running 32 bit. They send their data to a larger
> cluster that is running 64 bit. Should there be something special done in order
> to accommodate the difference?
How is the data sent? In almost every case, the translation should work
fine. I think 32-bit overflow should be your only concern here.
--
Bruce Momjian <bruce(at)momjian(dot)us<mailto:bruce(at)momjian(dot)us>> https://momjian.us<https://momjian.us>
EnterpriseDB https://enterprisedb.com<https://enterprisedb.com>
The usefulness of a cup is in its emptiness, Bruce Lee
From | Date | Subject | |
---|---|---|---|
Next Message | Susan Hurst | 2020-08-31 17:32:44 | Function Speed vs UI Function Speed |
Previous Message | Bruce Momjian | 2020-08-31 16:54:23 | Re: Numeric data types |