Oracle timestamp(6) truncated with postgresql 9.5 about oracle_fdw HOT 7 CLOSED

Sorry for the inconvenience.

Could you tell me the timestamp value that causes the error?

from oracle_fdw.

Oracle SQL Dev Tool shows me values like : 28/03/14 17:56:10,863000000

First tried with import schema, giving this error. I tried to map into a character varying(255) in postgresql, same issue. It worked fine in postgresql 9.4.

from oracle_fdw.

Hmm, it works for me.

In Oracle:

SQL> CREATE TABLE tstest (id NUMBER(5) PRIMARY KEY, ts TIMESTAMP(6) NOT NULL);
SQL> INSERT INTO tstest (id, ts) VALUES (1, to_timestamp('2014-03-28 17:56:10.863000000', 'YYYY-MM-DD HH24:MI:SS.FF'));
SQL> COMMIT;

In PostgreSQL:

test=> CREATE FOREIGN TABLE tstest (id integer NOT NULL, ts timestamp(6) NOT NULL) SERVER oracle OPTIONS (table 'TSTEST');
test=> SELECT * FROM tstest;
┌────┬─────────────────────────┐
│ id │           ts            │
├────┼─────────────────────────┤
│  1 │ 2014-03-28 17:56:10.863 │
└────┴─────────────────────────┘
(1 row)

Could you tell me the exact hex value of the Oracle date field?
You can get it with the DUMP function, in my example like this:

SQL> SELECT dump(ts, 16) FROM tstest WHERE id = 1;
DUMP(TS,16)
--------------------------------------------------------------------------------
Typ=180 Len=11: 78,72,3,1c,12,39,b,33,70,55,c0

Alternatively, can you come up with a sequence of SQL statements to reproduce the problem?

from oracle_fdw.

Here is the result :

Typ=180 Len=11: 78,72,3,1c,12,39,b,33,70,55,c0

So same value as yours. Did you run your tests with postgresql 9.5 ?

from oracle_fdw.

Ok, I can reproduce the error now, but only with lc_messages = fr_FR.UTF-8.
I'll look into it.

from oracle_fdw.

I have pushed 3fa9d98 that should fix the problem.
Can you check?

from oracle_fdw.

👍 Fixed ! Thanks !

from oracle_fdw.