Re: error messages (autovaccum canceled and syntax errors) while loading a DUMP

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Matthias Apitz <guru(at)unixarea(dot)de>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: error messages (autovaccum canceled and syntax errors) while loading a DUMP
Date: 2020-06-25 20:25:00
Message-ID: 2291754.1593116700@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Matthias Apitz <guru(at)unixarea(dot)de> writes:
> On Thursday, 25 June 2020 21:41:54 CEST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> wrote:
>> regardless of the exact details, it seems like the most likely theory
>> about what is happening is that the dump file is corrupt and the
>> corruption is causing the de-gzipped output to be missing or
>> duplicating chunks of text.

> I think, that a
> gzip -dc foo
> will work, regardless of the file names extensiom not beeing .gz

Agreed, that gzip command won't care. I was concerned about what
might've happened in between.

> I think also, if the file have been corrupted on transport, gzip -dc ...
> would complain about.

Maybe. It'd be unlikely to be able to tell before reaching the CRC
checksum at the end of the file, and it seems likely that it never
does reach the end in this usage ... are you allowing the psql run
to complete? Even if you are, you might miss gzip's one-line complaint
in between all the whining from psql.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Lewis 2020-06-25 20:51:12 Re: SQL delete and update at the same time
Previous Message Matthias Apitz 2020-06-25 20:04:57 Re: error messages (autovaccum canceled and syntax errors) while loading a DUMP