Re: pg_dump crashes

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Nico De Ranter <nico(dot)deranter(at)esaturnus(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump crashes
Date: 2020-05-22 15:33:29
Message-ID: 9424642a-a1ff-7d2e-9f8f-ec4e6d50ca4e@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 5/22/20 8:13 AM, Nico De Ranter wrote:
>
>

>
>
> bacula=# SELECT md5 FROM public.file where fileid = 4557430888798830399;
>  md5
> -----
> (0 rows)
> So that fileid is bogus too (max(bigint) I assume)

No:

select 4557430888798830399::bigint;
int8
---------------------
4557430888798830399
(1 row)

It means it cannot find that fileid. I putting that down to file corruption.

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-05-22 15:36:19 Re: pg_dump crashes
Previous Message Tom Lane 2020-05-22 15:24:41 Re: Query returns no rows in pg_basebackup cluster