| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | and7ua(at)gmail(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Error in pg_restore (could not close data file: Success) |
| Date: | 2020-10-21 04:45:15 |
| Message-ID: | 20201021.134515.264010492905725140.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Tue, 20 Oct 2020 13:48:25 +0300, Andrii Tkach <and7ua(at)gmail(dot)com> wrote in
> Hello,
> After restoring 'directory' backup with pg_restore (PostgreSQL 10.6) I've
> got a message:
> pg_restore: [directory archiver] could not close data file: Success
> pg_restore: [parallel archiver] a worker process died unexpectedly
> In this thread:
> https://www.postgresql.org/message-id/CAFcNs%2Bos5ExGvXMBrBBzzuJJamoHt5-zdJdxX39nkVG0KUxwsw%40mail.gmail.com
> there is only one answer. I'm interesting, is it normal behaivor of
> pg_restore and backup restored normaly or not ?
That would be a broken compressed file, maybe caused by disk full.
This reminded me of a thread. The issue above seems to be the same
with this:
Me> Hmm. Sounds reasonable. I'm going to do that. Thanks!
But somehow that haven't happened, I'll come up with a new version.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tang, Haiying | 2020-10-21 06:06:52 | RE: Use of "long" in incremental sort code |
| Previous Message | Amit Kapila | 2020-10-21 04:41:06 | Re: Add statistics to pg_stat_wal view for wal related parameter tuning |