Re: pg_dump crashes

On Fri, May 22, 2020 at 5:02 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)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?

>
> >
> > Nico
> >
> >
> >
>
> >
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
>
>

--

Nico De Ranter

Operations Engineer

T. +32 16 38 72 10

<http://www.esaturnus.com>

<http://www.esaturnus.com>

eSATURNUS
Philipssite 5, D, box 28
3001 Leuven – Belgium

T. +32 16 40 12 82
F. +32 16 40 84 77
www.esaturnus.com

<http://www.esaturnus.com/>

*For Service & Support :*

Support Line Belgium: +32 2 2009897

Support Line International: +44 12 56 68 38 78

Or via email : medical(dot)services(dot)eu(at)sony(dot)com