Re: Dump
От | Mihai Gheorghiu |
---|---|
Тема | Re: Dump |
Дата | |
Msg-id | 000c01bfd0a9$ede4aba0$4116113f@new6 обсуждение исходный текст |
Ответ на | Dump (Trurl McByte <trurl@realtor3d.odessa.ua>) |
Ответы |
Re: Dump
|
Список | pgsql-general |
pg_dump... outputs nothing!? I did it with -f filename too, and the file is empty. All the files in the database were exported from MSAccess using the psqlODBC driver directly into Postgres, with no prior declaration. Size of the file in question: 5MB, 7062 rows. Name of table: tblReservations. I wanted to re-create the error today, but I got something different: pg_dump tantest > tantest.bak pqWait() -- connection not open PQendcopy: resetting connection SQL query to dump the contents of Table 'tblTransactionsUnprocessed' did not execute correctly. After we read all the table contents from the backend, PQendcopy failed. Explanation from backend: ' The Data Base System is starting up '. The query was: 'COPY "tblTransactionsUnprocessed" TO stdout; '. tbl TransactionsUnprocessed: 98kB, 378 rows BTW, this leaves temp file traces in the database. Next time I want to try pg_dump I get a "No such file or directory" error. I look with pgaccess and there is a table with that name shown, only no such file in the tantest directory. Tried once again and I got no error!!! Any idea what's going on? Then: createdb newtest psql -e newtest < tantest.bak Crashes in tblTransactions (3.5MB, 117krows) with: COPY "tblTransactions" FROM stdin ERROR: copy: line 116229, Bad timestamp external representation '2000-05-15 00800:00-08' PQendcopy: resetting connection If there was such an error in the original table, shouldn't it be shown by pg_dump? >Mihai Gheorghiu <tanhq@bigplanet.com> writes: >>>> I wanted to back up a database prior to upgrading to 7.0.2 >>>> pg_dump dbname > dbname.bak >>>> FATAL 1: Memory exhausted in AllocSetAlloc() >>>> PQendcopy: resetting connection >>>> SQL query to dump the contents of Table 'tblname' did not execute >>>> correctly. >>> >>> Hmm, what version are you using now? COPY used to have a memory leak >>> problem according to the CVS logs, but that was long ago (pre-6.4). > >> 7.0 on RH6.1 > >OK, so much for the old-version theory. What is the full declaration of >table 'tblname'? (Easiest way to get it is pg_dump -s -t tblname dbname.) >Also, how many rows in the table? > > regards, tom lane
В списке pgsql-general по дате отправления: