Re: BUG #15304: Problem when replicating Floating point timestamps toint64 timestamps - Mailing list pgsql-bugs

From Vasilis Ventirozos
Subject Re: BUG #15304: Problem when replicating Floating point timestamps toint64 timestamps
Date
Msg-id 0464D6EE-95D5-4CA0-90D8-BE91C0F2CF53@gmail.com
Whole thread Raw
In response to Re: BUG #15304: Problem when replicating Floating point timestampsto int64 timestamps  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs

> On 27 Jul 2018, at 20:40, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>
> On 2018-Jul-27, PG Bug reporting form wrote:
>
>> While testing a migration procedure on a database (v9.6.9) from floating
>> point datetimes to int64 (v9.6.9) using pglogical i saw that after the
>> initial data sync all the subsequent replicated rows containing dates are
>> getting nonsensical datetime values in the subscriber.
>> I've read:
>> https://www.postgresql.org/message-id/flat/26788.1487455319%40sss.pgh.pa.us#26788.1487455319@sss.pgh.pa.us
>> So I know that this is not something new, but i was wondering if there is
>> any way around this,
>
> As I recall, pglogical has a way to indicate transmission of data using
> the text representation rather than binary, which should fix this
> problem.
>
> --
> Álvaro Herrera                https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

That worked.
Thanks !

Vasilis Ventirozos
OmniTI Computer Consulting Inc.

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #15304: Problem when replicating Floating point timestampsto int64 timestamps
Next
From: Michael Paquier
Date:
Subject: Re: BUG #15303: Postgres fail to start if pg_wal is symlink, andworks when it's a junction point