MeetMe / dump_fdw

Foreign Data Wrapper for Postgres Dump Files
BSD 3-Clause "New" or "Revised" License
55 stars 6 forks source link

Problem with type #2

Open WMP opened 9 years ago

WMP commented 9 years ago

I create database dump:

pg_dump -F c --blobs -f "ebicdb.dmp" ebicdb

And foreign table:

CREATE FOREIGN TABLE outqueue_y2014m01c (
    id_outqueue integer,
    id_route character(36),
    id_structure character(36),
    id_msg character(36),
    id_msg_parent character(36),
    id_msg_internal character varying(256),
    id_dst character(36),
    id_src character(36),
    date_in timestamp without time zone,
    date_out timestamp without time zone,
    status smallint,
    endpoint character varying(500),
    out_filename character varying(500),
    status_info text,
    message_type smallint,
    id_msg_link character(36),
    original_payload_checksum character(40),
    original_payload_name character varying(128)
) SERVER dump_server
  OPTIONS (
    file_name '/var/lib/postgresql/ebicdb.dmp',
    schema_name 'public',
    relation_name 'outqueue_y2014m01'
  )
;

When i want to execute:

select * from outqueue_y2014m01c;

i have error:

ERROR:  invalid input syntax for type timestamp: "2014-02-01 00.909"

When i execute select * from outqueue_y2014m01 on database ebicdb i have results without problem.

I can execute:

select * from outqueue_y2014m01c limit 10;
select * from outqueue_y2014m01c limit 100;
select * from outqueue_y2014m01c limit 99999;
select * from outqueue_y2014m01c limit 300032;

witout error, but i cannot execute:

select * from outqueue_y2014m01c limit 300033;
ERROR:  invalid input syntax for type timestamp: "2014-02-01 00.909"

This is row 300033 from normal database:

id_outqueue |               id_route               |
id_structure             |                id_msg |
id_msg_parent             | id_msg_internal |
id_dst                | id_src                |         date_in
| date_out         | status | endpoint | out_filename | status_info |
message_type | id_msg_link | original_payload_checksum         |
original_payload_name
-------------+--------------------------------------+--------------------------------------+--------------------------------------+--------------------------------------+-----------------+--------------------------------------+--------------------------------------+-------------------------+-------------------------+--------+----------+--------------+-------------+--------------+-------------+------------------------------------------+-----------------------
  2020502208 | 9aeebbdd-da32-4df1-881e-479477b20964 |
590e19a3-a184-46ac-b2ff-c5cf105f51c2 |
f8f931a2-fc4b-43cf-9315-bc3a3be81fa1 |
107abb92-3203-4331-b510-5d2088f14cd0 | 223/14/M        |
B1AA1BF7-0C1A-11DB-A11F-2D8072E8B6EB |
ca611421-3b01-4171-afd5-bce91c9e27a8 | 2014-02-01 00:21:24.909 |
2014-02-01 00:21:28.014 |     20 |          | |             |
7 |             | 396c2c24f6a02dfbb01840d1813b105388e1ce3d |
RPS_20140201_0015.TXT
(1 row)
jonahharris commented 9 years ago

I have an idea of what this could be. What happens if you only dump that table? Does this still occur? If so, is it on the same or a different row?