-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I'm testing pg_migrator, and running into an annoyance with timestamps
while trying to verify the conversion. My steps were:
install pg_migrator under 8.4 cluster
run pg_migrator in copy mode -- pg_migrator reports success
start up 8.4 cluster
restore pg_control file in 8.3 cluster
start 8.3 cluster
run pg_dump from 8.4 against both 8.3 and 8.4 clusters
compare the dump files
diffs:
1. Two functions were left in the 8.4 databasepg_toasttbl_drop(oid)pg_toasttbl_recreate(oid, oid)
2. Sequences had additional "START WITH 1"
3. All timestamps in the data that have two decimal places on seconds, but end with zero, in the 8.3 dump become one
decimalplace in the 8.4 dump
The first two items are not much of an issue, but the third makes
validation of the data very painful.
I have to apologize for missing it if this has been discussed already,
but was this change intentional, and if so is there any way to force the
old behavior?
Thanks,
Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iQIcBAEBCAAGBQJKdieMAAoJEDfy90M199hlX5cP/iedAGnua275aR+GBj3M7psp
x5ek93JMxs7U+MkWQ5ufcMbfhd5N+cRauZbnPAHoAa9yqdUanCubH+p2xqSlLOPn
QISf/P11uJKnUOE2AuVUXVso2bBlp6WBpSxt5DgcpjsXgXWXNGmoVwRLb67+ZwX8
Hp7Kmi+OQewNfHwwkpybWvshx5N/BCrNfNfL/gqdEJTPG/H/7YjTomkKQIwdZDAt
NhgSaNL/HcE9iISkkW1tlTNTZhCitow/6LIONQju5X6Un7aUWA8ke8AvWnobeieL
xqzQbkwxa8Xhi4Yk61omupdXyYhJDHsOG1WUe4vlResmaYpeTzv3ztlhrfvBaJzv
gom7B8xLmcwl3+znp0l78TDti2CcvgY5MThvTdymUFa0clYDf93bG8qHq90pw17P
URA0QGLDnhCJThmV9nugw2dgpJCISR2pqsi9YYCX6zLa2dUw9IMWAfZMjyP4K3kP
IzGUB8ppfRadOC5iavsoRdFwY6eClhU+jCTLlUkyN+KcmgJy5H1TwmrhBUEX0reW
jkDZvnTs1+fx4S+yfJQYPpcpxsNp0a8RFAmzWPAF8p7uLNjZUsJtOC3rWNiUGdF8
o8PQPur8xBB5FebmZ0o1ig1ncW6SFREJ8+r1pz/w78fKjlADSy80tEGySPjGRLIL
2cpDvGcfJfR5UyVhB5n1
=6fOT
-----END PGP SIGNATURE-----
