On 5/22/20 8:05 AM, Nico De Ranter wrote: > > On Fri, May 22, 2020 at 5:02 PM Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > > 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. > > > But that would be content of the database only. The should matter for > the application but not for a dump of the database, right?
I would think that depends on what '???????' is really representing.
In the database try:
SELECT md5 FROM public.file where fileid = 4557430888798830399;
bacula=# SELECT md5 FROM public.file where fileid = 4557430888798830399; md5 ----- (0 rows)
So that fileid is bogus too (max(bigint) I assume)