pg_basebackup + SSL error: bad length

2018-08-27 Thread Csaba Ragasits
Hello, I would like to create a streaming replication, when I'm trying the basebackup from the node1, I've the following errors: pg_basebackup -P -v -D ./main -h node1 -p 5432 -U repmgr pg_basebackup: initiating base backup, waiting for checkpoint to complete pg_basebackup: checkpoint completed

Re: pg_basebackup + SSL error: bad length

2018-08-27 Thread Csaba Ragasits
2018-08-27 16:08 GMT+02:00 Adrian Klaver : > Can you connect to node1 using psql with and without SSL? > > Where is node1 relative to the machine you are running pg_basebackup from? > > Just to be clear both Postgres instances are running 10.5, correct? > >> >> Every instances are same (10.5) vers

Re: pg_basebackup + SSL error: bad length

2018-08-28 Thread Csaba Ragasits
Hello, Only one copy is from the pg_basebackup on the machines. I have only a tablespace only a different location: /srv/pgdata/tbs_int303 I think I solved the problem: When I delete manually the /srv/pgdata/tbs_int303 folder, the pg_basebackup is running fine. Thank you for your help, Csaba

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

Re: PG8.3->10 migration data differences

2018-09-10 Thread Csaba Ragasits
you have any ideas how can I format the miliseconds too? Thx, Csaba 2018-09-10 12:00 GMT+02:00 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 migra

Re: PG8.3->10 migration data differences

2018-09-11 Thread Csaba Ragasits
me mark it as error. thx, Csaba 2018-09-10 16:21 GMT+02:00 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 s