| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Gilar Ginanjar <gilar(at)innovation-project(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Cc: | Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com> |
| Subject: | Re: Unexpected block ID found when reading data |
| Date: | 2021-08-03 15:30:54 |
| Message-ID: | 858a6487-7489-be9b-0b18-7e807dc8c63b@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 8/3/21 8:20 AM, Gilar Ginanjar wrote:
> Yes, i’ve found at some forums (DBeaver) that it is a bug on pg_restore.
The specific bug being?
> Hopefully so, so that I have hope to restore my data later.
>
>
> This is the output for "pg_restore —version”:
>
> pg_restore (PostgreSQL) 12.7
>
>
> And this are some "pg_restore -l -v dbdump.backup” output:
>
> ; dbname: mydb
> ; TOC Entries: 6487
> ; Compression: 3
> ; Dump Version: 1.14-0
> ; Format: CUSTOM
> ; Integer: 4 bytes
> ; Offset: 8 bytes
> ; Dumped from database version: 9.6.21
> ; Dumped by pg_dump version: 12.5
>
>
> Once again many thanks for the help. Really appreciate it.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-08-03 15:56:24 | Re: Unexpected block ID found when reading data |
| Previous Message | Gilar Ginanjar | 2021-08-03 15:20:10 | Re: Unexpected block ID found when reading data |