Re: pg_dump crashes
От | Adrian Klaver |
---|---|
Тема | Re: pg_dump crashes |
Дата | |
Msg-id | c1d837db-0bd8-5e41-d276-b74ab9d98920@aklaver.com обсуждение исходный текст |
Ответ на | Re: pg_dump crashes (Nico De Ranter <nico.deranter@esaturnus.com>) |
Ответы |
Re: pg_dump crashes
|
Список | pgsql-general |
On 5/22/20 7:55 AM, Nico De Ranter wrote: > Correct. > > If I run 'pg_dumpall --cluster 11/main --file=dump.sql' the end of the > file looks like: > > ###### cut here > 4557430888798830399 1061109567 1061109567 1061109567 1061109567 16191 \N > \N ?????????????????????????????? > 4557430888798830399 1061109567 1061109567 1061109567 1061109567 16191 \N > \N ?????????????????????????????? > \. > > ###### cut here > > If I run 'pg_dump --table=public.file --cluster 11/main > --file=dump-2.sql bacula' those lines are actually followed by about > 850 or so lines that look ok. I'm assuming the difference is due to > buffering. > However the fact that I do see a number of regular lines following this > may suggest it's just garbage in the table but not really causing the > issue afterall. Assuming the above matches: COPY public.file (fileid, fileindex, jobid, pathid, filenameid, deltaseq, markid, lstat, md5) the '????????????????????' would be for the md5 field. I'm going to say that is important. > > Nico > > > > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: