| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | v(dot)ventirozos(at)gmail(dot)com, 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 17:40:21 |
| Message-ID: | 20180727174021.n2r3cweflwn3ip4j@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vasilis Ventirozos | 2018-07-27 21:38:06 | Re: BUG #15304: Problem when replicating Floating point timestamps to int64 timestamps |
| Previous Message | PG Bug reporting form | 2018-07-27 17:31:02 | BUG #15304: Problem when replicating Floating point timestamps to int64 timestamps |