Re: Restoring a pg_dump fails with
От | Reiner Dassing |
---|---|
Тема | Re: Restoring a pg_dump fails with |
Дата | |
Msg-id | 3AE9262E.6191263F@wettzell.ifag.de обсуждение исходный текст |
Ответ на | Restoring a pg_dump fails with (Reiner Dassing <dassing@wettzell.ifag.de>) |
Ответы |
Re: Restoring a pg_dump fails with
|
Список | pgsql-admin |
Tom Lane wrote: > > Reiner Dassing <dassing@wettzell.ifag.de> writes: > > By upgrading von PostgreSQL 6.5.3 to 7.1.0 I restored a dump file by > > psql dbname <dbname.dump > > > After some time I get the following message: > > ERROR: copy: line 1638280, Memory exhausted in AllocSetAlloc(56) > > PQendcopy: resetting connection > > That shouldn't happen. Could we see the dump file? (Just the schema > commands, not the data itself...) > > regards, tom lane Dear Tom! Thank you for your help. Certainly I will give this short schema: \connect - postgres ... CREATE TABLE "wetter" ( "sensor_id" int4 NOT NULL, "epoche" datetime NOT NULL, "wert" float4 NOT NULL); REVOKE ALL on "wetter" from PUBLIC; GRANT ALL on "wetter" to "postgres"; COPY "wetter" FROM stdin; 8 Thu Mar 02 02:34:02 2000 GMT -0.4 10 Thu Mar 02 02:34:02 2000 GMT 95 3 Thu Mar 02 02:34:02 2000 GMT 193.6 11 Thu Mar 02 02:34:02 2000 GMT 97.7 2 Thu Mar 02 02:34:02 2000 GMT 251.5 13 Thu Mar 02 02:34:02 2000 GMT 940.9 1 Thu Mar 02 02:34:02 2000 GMT 283.2 6 Thu Mar 02 02:34:02 2000 GMT 0.8 .... \. I have witten a script to convert these COPY statements to INSERTs and this worked! But it took a long time during night time. -- Mit freundlichen Gruessen / With best regards Reiner Dassing --------------------------------------------------- | Bundesamt fuer Kartographie und Geodaesie | Fundamentalstation Wettzell | Sackenrieder Str. 25 | D-93444 Koetzting | | Tel: (+49) (0)9941/603-112 | Fax: (+49) (0)9941/603-222 | Zentrale: (+49) (0)9941/603-0 | E-mail: dassing@wettzell.ifag.de | URL: http://www.ifag.de ---------------------------------------------------
В списке pgsql-admin по дате отправления: