postgres server process crashes when using odbc_fdw

Version 10.5
AWS Linux
Foreign server: Db2 on Linux 10.5.9
carto_odbc
unix_odbc

I am able to build odbc_fdw extension, register the extension and also create foreign server.
I also created foreign table.

When I run a sql 'select * from odbctest' postgres crashes, generate a core file.

2018-10-16 20:03:42.494 EDT [4639] LOG: listening on IPv4 address "127.0.0.1", port 5432
2018-10-16 20:03:42.498 EDT [4639] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
2018-10-16 20:03:42.513 EDT [4640] LOG: database system was shut down at 2018-10-16 20:00:05 EDT
2018-10-16 20:03:42.517 EDT [4639] LOG: database system is ready to accept connections
2018-10-16 20:05:11.777 EDT [4639] LOG: server process (PID 4787) was terminated by signal 11: Segmentation fault
2018-10-16 20:05:11.777 EDT [4639] DETAIL: Failed process was running: select * from odbctest ;
2018-10-16 20:05:11.777 EDT [4639] LOG: terminating any other active server processes
2018-10-16 20:05:11.777 EDT [4644] WARNING: terminating connection because of crash of another server process
2018-10-16 20:05:11.777 EDT [4644] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2018-10-16 20:05:11.777 EDT [4644] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2018-10-16 20:05:11.777 EDT [4816] WARNING: terminating connection because of crash of another server process
2018-10-16 20:05:11.777 EDT [4816] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2018-10-16 20:05:11.777 EDT [4816] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2018-10-16 20:05:11.778 EDT [4639] LOG: all server processes terminated; reinitializing
2018-10-16 20:05:11.847 EDT [4818] LOG: database system was interrupted; last known up at 2018-10-16 20:03:42 EDT
2018-10-16 20:05:11.860 EDT [4818] LOG: database system was not properly shut down; automatic recovery in progress
2018-10-16 20:05:11.863 EDT [4818] LOG: redo starts at 5/7F9971A0
2018-10-16 20:05:11.863 EDT [4818] LOG: invalid record length at 5/7F9971D8: wanted 24, got 0
2018-10-16 20:05:11.863 EDT [4818] LOG: redo done at 5/7F9971A0
2018-10-16 20:05:11.877 EDT [4639] LOG: database system is ready to accept connections