On Fri, Jan 20, 2017 at 10:44 Periko Support <[email protected]> wrote:
> Exist a way to fix this or we have to manually fix the db? I believe you can get around this issue by disabling the strict_checking option (I think that's the name) on your sync. You can also do mildly dangerous things like swapping "attnum" values around between the rows Postgres uses to track the columns on your tables in the pg_attribute system catalog, but I wouldn't recommend it. rls -- :wq
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
