I think I've found the culprit of the problem.
I have a field which is varchar from the source DB while on the destination DB its integer. On Mon, May 7, 2018 at 2:39 PM, David G. Johnston <david.g.johnston@xxxxxxxxx> wrote:
On Sunday, May 6, 2018, tango ward <tangoward15@xxxxxxxxx> wrote:Yes, my apologies.May I also ask if there's a limitation for the number of timestamp with timezone fields in a table?Not one that is likely to matter in practice. There's a page discussing limitations on the website/docs somewhere if you wish to find out more.David J.