| From: | Vasilis Ventirozos <v(dot)ventirozos(at)gmail(dot)com> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15304: Problem when replicating Floating point timestamps to int64 timestamps |
| Date: | 2018-07-27 21:38:06 |
| Message-ID: | 0464D6EE-95D5-4CA0-90D8-BE91C0F2CF53@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 27 Jul 2018, at 20:40, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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(dot)1487455319%40sss(dot)pgh(dot)pa(dot)us#26788(dot)1487455319(at)sss(dot)pgh(dot)pa(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-07-28 00:10:12 | Re: BUG #15182: Canceling authentication due to timeout aka Denial of Service Attack |
| Previous Message | Alvaro Herrera | 2018-07-27 17:40:21 | Re: BUG #15304: Problem when replicating Floating point timestamps to int64 timestamps |