Re: pg_dump crashes - Mailing list pgsql-general

From Adrian Klaver
Subject Re: pg_dump crashes
Date
Msg-id b70664d0-1e40-ef32-1fe2-b5fc4d061391@aklaver.com
Whole thread Raw
In response to Re: pg_dump crashes  (Nico De Ranter <nico.deranter@esaturnus.com>)
Responses Re: pg_dump crashes
List pgsql-general
On 5/22/20 8:17 AM, Nico De Ranter wrote:
> 
> 
> On Fri, May 22, 2020 at 5:14 PM Adrian Klaver <adrian.klaver@aklaver.com 
> <mailto:adrian.klaver@aklaver.com>> wrote:
> 
>     On 5/22/20 8:05 AM, Nico De Ranter wrote:
>      >
> 
>      >
>      >     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?
> 
>     Also what does:
> 
>     \d public.file
> 
>     show?
> 
>     In particular are there any triggers on the table?
> 
> 
> bacula=# \d public.file
>                                   Table "public.file"
>     Column   |   Type   | Collation | Nullable |               Default
> ------------+----------+-----------+----------+--------------------------------------
>   fileid     | bigint   |           | not null | 
> nextval('file_fileid_seq'::regclass)
>   fileindex  | integer  |           | not null | 0
>   jobid      | integer  |           | not null |
>   pathid     | integer  |           | not null |
>   filenameid | integer  |           | not null |
>   deltaseq   | smallint |           | not null | 0
>   markid     | integer  |           | not null | 0
>   lstat      | text     |           | not null |
>   md5        | text     |           | not null |
> Indexes:
>      "file_pkey" PRIMARY KEY, btree (fileid)
>      "file_jobid_idx" btree (jobid)
>      "file_jpfid_idx" btree (jobid, pathid, filenameid)
> 
> 
> 
> Following up on the max(bigint), I tried
> 
>     SELECT md5 FROM public.file where fileid >2087994666;
> 
> and got
> 
>     ERROR:  compressed data is corrupted
> 
> So it does look like those entries are killing it.  Now for the 
> million-dollar question: how do I get them out?

Do you have recent previous backup?

> 
> Nico
> 
> -- 
> 
> Nico De Ranter
> 
> Operations Engineer
> 



-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: pg_dump crashes
Next
From: Adrian Klaver
Date:
Subject: Re: pg_dump crashes