Re: PG8.3->10 migration data differences

2018-09-11 Thread Adrian Klaver
On 9/11/18 1:41 AM, Csaba Ragasits wrote: Hello, We would like to migrate from 8.3 to 10 version. We've hundreds databases with different structures. That reason we're working on an automatic data comparing process. I've found the following storage settings: - pg83: Date/time type storage:  

Re: PG8.3->10 migration data differences

2018-09-11 Thread Ron
Then fix your field-based data comparing mechanism. On 09/11/2018 03:41 AM, Csaba Ragasits wrote: Hello, We would like to migrate from 8.3 to 10 version. We've hundreds databases with different structures. That reason we're working on an automatic data comparing process. I've found the

Re: PG8.3->10 migration data differences

2018-09-11 Thread Csaba Ragasits
Hello, We would like to migrate from 8.3 to 10 version. We've hundreds databases with different structures. That reason we're working on an automatic data comparing process. I've found the following storage settings: - pg83: Date/time type storage: 64-bit integers - pg10: Date/time

Re: PG8.3->10 migration data differences

2018-09-10 Thread Adrian Klaver
On 9/10/18 6:43 AM, Csaba Ragasits wrote: I think I found the solution. When I set this parameter on the pg10 client connection, the pg10 REAL value format same as the pg83 value: SET extra_float_digits = 0; Interesting, because the default value is 0 in the postgresql.conf:

Re: PG8.3->10 migration data differences

2018-09-10 Thread Adrian Klaver
On 9/10/18 6:43 AM, Csaba Ragasits wrote: I think I found the solution. When I set this parameter on the pg10 client connection, the pg10 REAL value format same as the pg83 value: In your previous post you mentioned both 9.3 and 8.3. Is 8.3 the actual version you are migrating from? SET

Re: PG8.3->10 migration data differences

2018-09-10 Thread Tom Lane
"Peter J. Holzer" writes: > On 2018-09-10 11:57:42 +0300, Achilleas Mantzios wrote: >> On 10/09/2018 11:22, Csaba Ragasits wrote: >>> Field type: REAL >>> pg93: 2.2 >>> pg10: 2.2005 >> Those have to do with rounding. Precision for real is 6 decimal >> digits. Your difference is on the 8-th

Re: PG8.3->10 migration data differences

2018-09-10 Thread Csaba Ragasits
I think I found the solution. When I set this parameter on the pg10 client connection, the pg10 REAL value format same as the pg83 value: SET extra_float_digits = 0; Interesting, because the default value is 0 in the postgresql.conf: #extra_float_digits = 0 # min -15, max 3 Do

Re: PG8.3->10 migration data differences

2018-09-10 Thread Peter J. Holzer
On 2018-09-10 11:57:42 +0300, Achilleas Mantzios wrote: > On 10/09/2018 11:22, Csaba Ragasits wrote: > Hello, > > We would like to migrate our old databases to new postgres server, > with the simple backup-restore process. The process run fine > without errors but when we're 

Re: PG8.3->10 migration data differences

2018-09-10 Thread Achilleas Mantzios
On 10/09/2018 11:22, Csaba Ragasits wrote: Hello, We would like to migrate our old databases to new postgres server, with the simple backup-restore process. The process run fine without errors but when we're  checking the source and the migrated datas as field level, we found the following

PG8.3->10 migration data differences

2018-09-10 Thread Csaba Ragasits
Hello, We would like to migrate our old databases to new postgres server, with the simple backup-restore process. The process run fine without errors but when we're checking the source and the migrated datas as field level, we found the following differences: For example: Field type: TIMESTAMP