Thread: Impossible to import pg_dumpall from 7.2.2 to 7.3b1
Hi, This is my configuration : template1=# select version(); version ---------------------------------------------------------------PostgreSQL 7.3b1 on i686-pc-linux-gnu, compiled by GCC 2.95.4 (1 row) 128 Mb of RAM with a PIII933 Linux debian woody As usual I have done like explain is the doc ... pg_dumpall of my 7.2.2 database ... But when I try to import it inside 7.3b1 I get this : (seems that the copy command is not fully compatible with the 7.2.2 pg_dumpall ?) Many thinks like this : (I have only copied some parts ...) Size of the dump about 1.5 Gb ... Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015274: invalid command \nPour Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015274: invalid command \n<b> psql:/tmp/dump_mybase.txt:1015274: invalid command \N psql:/tmp/dump_mybase.txt:1015274: invalid command \N psql:/tmp/dump_mybase.txt:1015274: invalid command \N Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015275: invalid command \nLa psql:/tmp/dump_mybase.txt:1015275: invalid command \N psql:/tmp/dump_mybase.txt:1015275: invalid command \N psql:/tmp/dump_mybase.txt:1015275: invalid command \N Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015276: invalid command \nLa psql:/tmp/dump_mybase.txt:1015276: invalid command \N psql:/tmp/dump_mybase.txt:1015276: invalid command \N psql:/tmp/dump_mybase.txt:1015276: invalid command \N psql:/tmp/dump_mybase.txt:1015277: ERROR: parser: parse error at or near "1038" at character 1 Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015277: invalid command \n Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015277: invalid command \n* Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015277: invalid command \n Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015277: invalid command \n Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015277: invalid command \n psql:/tmp/dump_mybase.txt:1015277: invalid command \N psql:/tmp/dump_mybase.txt:1015277: invalid command \N psql:/tmp/dump_mybase.txt:1015277: invalid command \N Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015278: invalid command \n<STRONG>Cette psql:/tmp/dump_mybase.txt:1015278: invalid command \N psql:/tmp/dump_mybase.txt:1015278: invalid command \N psql:/tmp/dump_mybase.txt:1015278: invalid command \N Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015279: invalid command \n psql:/tmp/dump_mybase.txt:1015279: invalid command \N psql:/tmp/dump_mybase.txt:1015279: invalid command \N psql:/tmp/dump_mybase.txt:1015279: invalid command \N Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015280: invalid command \n<b>Attention Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015280: invalid command \n2. psql:/tmp/dump_mybase.txt:1015280: invalid command \N psql:/tmp/dump_mybase.txt:1015280: invalid command \N psql:/tmp/dump_mybase.txt:1015280: invalid command \N Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015281: invalid command \nInterdit psql:/tmp/dump_mybase.txt:1015281: invalid command \N psql:/tmp/dump_mybase.txt:1015281: invalid command \N psql:/tmp/dump_mybase.txt:1015281: invalid command \N Query buffer reset (cleared). psql:/tmp/dump_mybase.txt:1015286: invalid command \nClip psql:/tmp/dump_mybase.txt:1015286: invalid command \N psql:/tmp/dump_mybase.txt:1015286: invalid command \N psql:/tmp/dump_mybase.txt:1015286: invalid command \N psql:/tmp/dump_mybase.txt:1015287: invalid command \. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. Showing on tuples. Tuples only is off. psql:dump_mybase.txt:2736773: invalid command \N psql:dump_mybase.txt:2736774: ERROR: parser: parse error at or near "9" at character 1 psql:dump_mybase.txt:2736774: ERROR: parser: parse error at or near "4405004" at character 1 psql:dump_mybase.txt:2736774: ERROR: parser: parse error at or near "7327180" at character 1 psql:dump_mybase.txt:2736774: invalid command \N psql:dump_mybase.txt:2736774: invalid command \N psql:dump_mybase.txt:2736775: invalid command \N psql:dump_mybase.txt:2736775: invalid command \N psql:dump_mybase.txt:2736776: invalid command \N psql:dump_mybase.txt:2736776: invalid command \N psql:dump_mybase.txt:2736777: invalid command \N psql:dump_mybase.txt:2736777: invalid command \N psql:dump_mybase.txt:2736778: invalid command \N psql:dump_mybase.txt:2736778: invalid command \N psql:dump_mybase.txt:2736779: ERROR: parser: parse error at or near "w" at character 1 psql:dump_mybase.txt:2736779: ERROR: parser: parse error at or near "4405004" at character 1 psql:dump_mybase.txt:2736779: ERROR: parser: parse error at or near "7327180" at character 1 psql:dump_mybase.txt:2736779: invalid command \N psql:dump_mybase.txt:2736779: invalid command \N psql:dump_mybase.txt:2736780: ERROR: parser: parse error at or near "w" at character 1 psql:dump_mybase.txt:2736780: ERROR: parser: parse error at or near "4405004" at character 1 psql:dump_mybase.txt:2736780: ERROR: parser: parse error at or near "7327180" at character 1 psql:dump_mybase.txt:2736780: invalid command \N psql:dump_mybase.txt:2736780: invalid command \N psql:dump_mybase.txt:2736781: invalid command \N psql:dump_mybase.txt:2736781: invalid command \N psql:dump_mybase.txt:2736782: invalid command \N psql:dump_mybase.txt:2736782: invalid command \N psql:dump_mybase.txt:2736783: ERROR: parser: parse error at or near "w" at character 1 psql:dump_mybase.txt:2736783: ERROR: parser: parse error at or near "4405004" at character 1 psql:dump_mybase.txt:2736783: ERROR: parser: parse error at or near "7327180" at character 1 psql:dump_mybase.txt:2736783: invalid command \N psql:dump_mybase.txt:2736783: invalid command \N psql:dump_mybase.txt:2736784: invalid command \N psql:dump_mybase.txt:2736784: invalid command \N psql:dump_mybase.txt:2736785: invalid command \N psql:dump_mybase.txt:2736785: invalid command \N psql:dump_mybase.txt:2736786: invalid command \N psql:dump_mybase.txt:2736786: invalid command \N psql:dump_mybase.txt:2736787: invalid command \. You are now connected as new user herve. psql:dump_mybase.txt:2736797: ERROR: parser: parse error at or near "w" at character 1 psql:dump_mybase.txt:2880938: invalid command \. You are now connected as new user postgres. psql:dump_mybase.txt:2880948: ERROR: parser: parse error at or near "110013570705" at character 1 Query buffer reset (cleared). psql:dump_mybase.txt:2882296: \r: extra argument '7116' ignored psql:dump_mybase.txt:2882296: \r: extra argument '2001-08-07' ignored psql:dump_mybase.txt:2882296: \r: extra argument 'nl42txt' ignored psql:dump_mybase.txt:2882774: ERROR: parser: parse error at or near "lo1252386" at character 1 psql:dump_mybase.txt:3719939: invalid command \ psql:dump_mybase.txt:3719940: invalid command \ psql:dump_mybase.txt:3719941: invalid command \ psql:dump_mybase.txt:3719942: invalid command \ psql:dump_mybase.txt:3719943: invalid command \ psql:dump_mybase.txt:3719944: invalid command \ psql:dump_mybase.txt:3719945: invalid command \ psql:dump_mybase.txt:3719946: invalid command \. You are now connected as new user postgres. psql:dump_mybase.txt:3747485: invalid command \. Finish like this all the time ! :( psql:dump_mybase.txt:16596289: invalid command \N server closed the connection unexpectedly This probably means the server terminated abnormally before or whileprocessing the request. Any ideas ? Regards, -- Hervé
Hervé Piedvache <herve@elma.fr> writes:
> But when I try to import it inside 7.3b1 I get this :
> (seems that the copy command is not fully compatible with the 7.2.2
> pg_dumpall ?)
> Many thinks like this : (I have only copied some parts ...)
> Size of the dump about 1.5 Gb ...
> Query buffer reset (cleared).
> psql:/tmp/dump_mybase.txt:1015274: invalid command \nPour
> Query buffer reset (cleared).
It seems pretty clear that the COPY command itself failed, leaving psql
trying to interpret the following data as SQL commands. But you have
not shown us either the COPY command or the error message it generated,
so there's not a lot we can say about it...
regards, tom lane
Dear Tom, >> <herve@elma.fr> writes: >> But when I try to import it inside 7.3b1 I get this : >> (seems that the copy command is not fully compatible with the 7.2.2 >> pg_dumpall ?) >> >> Many thinks like this : (I have only copied some parts ...) >> Size of the dump about 1.5 Gb ... >> >> Query buffer reset (cleared). >> psql:/tmp/dump_mybase.txt:1015274: invalid command \nPour >> Query buffer reset (cleared). > >It seems pretty clear that the COPY command itself failed, leaving psql >trying to interpret the following data as SQL commands. But you have >not shown us either the COPY command or the error message it generated, >so there's not a lot we can say about it... > >regards, tom lane OK I have (hope) find the trouble ... may be a mistake from my part but which was running with v7.2.2 ... (I think I have to alter my table with default current_date ...) I have this error message : psql:dump.7.2.2.txt:304: ERROR: Column "datecrea" is of type date but default expression is of type timestamp with time zone You will need to rewrite or cast the expression for the field : "datecrea" date DEFAULT now(), So after, the importation of the data are making errors messages because the previus table has not been created ... I'm right ? I have also a strange error : psql:dump.7.2.2.txt:1087: ERROR: function plpgsql_call_handler() does not return type language_handler psql:dump.7.2.2.txt:1126: ERROR: language "plpgsql" does not exist for those lines : -- -- TOC Entry ID 292 (OID 2083293) -- -- Name: "plpgsql_call_handler" () Type: FUNCTION Owner: postgres -- CREATE FUNCTION "plpgsql_call_handler" () RETURNS opaque AS '/usr/local/pgsql/lib/plpgsql.so', 'plpgsql_call_handler' LANGUAGE 'C'; -- -- TOC Entry ID 293 (OID 2083294) -- -- Name: plpgsql Type: PROCEDURAL LANGUAGE Owner: -- CREATE TRUSTED PROCEDURAL LANGUAGE 'plpgsql' HANDLER "plpgsql_call_handler" LANCOMPILER 'PL/pgSQL'; Hope this help ... Regards, -- Hervé