Insertions into postgres table with timestamp fail

[jimexist]

Caused by: java.sql.SQLException: Query failed (#20161201_103957_00022_n38hp): Batch entry 0 INSERT INTO "circle_test"."public"."tmp_presto_10e94267352a4161ae25844b67c6d505" VALUES ('Cup',12.2,1280424020000) was aborted.  Call getNextException to see the cause.

This happens when directly insert data via Presto into a postgres table with a timestamp column. It seems that the 1280424020000 value wasn't properly cast to timestamp type.

[jimexist]

This was the log from presto side:

2016-12-01T10:39:58.100Z	ERROR	SplitRunner-0-52	com.facebook.presto.execution.TaskExecutor	Error processing Split 20161201_103957_00022_n38hp.1.0-0  (start = 1480588797917, wall = 167 ms, cpu = 11 ms, calls = 4): JDBC_ERROR: Batch entry 0 INSERT INTO "circle_test"."public"."tmp_presto_10e94267352a4161ae25844b67c6d505" VALUES ('Cup',12.2,1280424020000) was aborted.  Call getNextException to see the cause.

[maciejgrzybek]

This is duplicated by #7747. I'm closing this in favor of the other one.