londiste doesn't copy all significant digits with double presicion data type

[martinmarques]

I'm working on a server migration with londiste. We've been having trouble with a table which has a unique constraint that always failed on getting applied. It's erroring about duplicate values which are not on the provider node.

Taking a pg_dump of the table in question showed that the tuples unique key were different on the provider.

Playing around I found that londiste uses the default value for extra_float_digits which is zero. This means some significant values for float fields get lost. This is very bad, as people would expect to have the same exact data copied over as what they have on the provider node.

Workaround is to just change the connection string on the root node (or on all nodes) so it sets extra_float_digits to 3. Just add something like option='-c extra_float_digits=3'