Re: pg_restore: [archiver] entry ID 0 out of range -- perhaps a corrupt TOC

Alexsandro Haag <[email protected]> Fri, 13 Apr 2018 08:25:00 -0300
Newsgroups gmane.comp.db.postgresql.brasil
Message-ID <399f2309-54a7-1916-16c5-bb6a9c9fb33b__20067.5420267091$1523618586$gmane$org@gmail.com>
This is a multi-part message in MIME format.
--===============0391157634391973051==
Content-Type: multipart/alternative;
 boundary="------------AD5F666C7CDAF9E8C17A7388"
Content-Language: pt-BR

This is a multi-part message in MIME format.
--------------AD5F666C7CDAF9E8C17A7388
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Em 13/04/2018 01:56, Sebastian Webber escreveu:
> O que acontece quando tu roda o comando abaixo?
> pg_restore --list arquivo.dump
Bom dia Sebastian,
   rodei aqui e exibe também a mesma mensagem:

pg_restore --list troll.cop
pg_restore: [archiver] entry ID 0 out of range -- perhaps a corrupt TOC


O retorno para outro dump (que está funcionando) seria como esse:
; Archive created at 2018-04-12 16:52:05 -03
;     dbname: Troll
;     TOC Entries: 9086
;     Compression: -1
;     Dump Version: 1.12-0
;     Format: CUSTOM
;     Integer: 4 bytes
;     Offset: 8 bytes
;     Dumped from database version: 9.2.4
;     Dumped by pg_dump version: 9.2.4


Obs.: Sim, dbname é Troll mesmo. Mas é coisa séria. rsrsrs

Alex

--------------AD5F666C7CDAF9E8C17A7388
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Em 13/04/2018 01:56, Sebastian Webber escreveu:
    <blockquote type="cite"
cite="mid:CACV2tSxJjkNN_1+1Xqvv+yvGPMVHCRneYOVcsdExQp5gGJ+qRw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>O que acontece quando tu roda o comando abaixo?<br>
            </div>
            <div><span style="font-family:monospace,monospace">pg_restore
                --list arquivo.dump</span><br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    Bom dia Sebastian,<br>
      rodei aqui e exibe também a mesma mensagem: <br>
    <br>
    <tt>pg_restore --list troll.cop </tt><tt><br>
    </tt><tt>pg_restore: [archiver] entry ID 0 out of range -- perhaps a
      corrupt TOC<br>
      <br>
      <br>
    </tt>O retorno para outro dump (que está funcionando) seria como
    esse:<br>
    <tt>; Archive created at 2018-04-12 16:52:05 -03</tt><tt><br>
    </tt><tt>;     dbname: Troll</tt><tt><br>
    </tt><tt>;     TOC Entries: 9086</tt><tt><br>
    </tt><tt>;     Compression: -1</tt><tt><br>
    </tt><tt>;     Dump Version: 1.12-0</tt><tt><br>
    </tt><tt>;     Format: CUSTOM</tt><tt><br>
    </tt><tt>;     Integer: 4 bytes</tt><tt><br>
    </tt><tt>;     Offset: 8 bytes</tt><tt><br>
    </tt><tt>;     Dumped from database version: 9.2.4</tt><tt><br>
    </tt><tt>;     Dumped by pg_dump version: 9.2.4</tt><tt><br>
    </tt><br>
    <br>
    Obs.: Sim, dbname é Troll mesmo. Mas é coisa séria. rsrsrs<br>
    <br>
    Alex<br>
  </body>
</html>

--------------AD5F666C7CDAF9E8C17A7388--

--===============0391157634391973051==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcGdici1nZXJh
bCBtYWlsaW5nIGxpc3QKcGdici1nZXJhbEBsaXN0YXMucG9zdGdyZXNxbC5vcmcuYnIKaHR0cHM6
Ly9saXN0YXMucG9zdGdyZXNxbC5vcmcuYnIvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3BnYnIt
Z2VyYWw=

--===============0391157634391973051==--