Re: Unable to dump database using pg_dump

From: Adam Dear <adear(at)usnx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org
Subject: Re: Unable to dump database using pg_dump
Date: 2008-06-12 16:06:40
Message-ID: 48514990.7070802@usnx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I downloaded a hex editor, but honestly, I can't make heads or tails of
what I'm looking at. I'm not sure what needs changing.

Also, FYI, you mentioned that you thought I had deleted the record with
ctid=(0,2). I did delete that, but thats what caused the database to
not work. I restored a backup copy of the data directory I had made
yesterday morning before I started messing with it.

If I restored the data directory again wouldn't that undo the Vacuum
Freeze command that I did that has locked the database into the state
that it is in now?

Tom Lane wrote:
> Adam Dear <adear(at)usnx(dot)net> writes:
>> I'm comfortable enough with it that I can edit it if I can find exactly
>> what to edit. Whats the best way to edit the file? I've opened it using:
>
>> vim -b 1260
>
>> Here is what is at the end of the block in the file. If you could point
>> me in the right direction, I'd appreciate it.
>
> I think you need to change T^B to ^B^@ ... though I agree with Alvaro
> that a hex editor would be a more comfortable tool.
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-06-12 16:15:36 Re: Heavily fragmented table and index data in 8.0.3
Previous Message Joshua D. Drake 2008-06-12 16:02:17 Re: Heavily fragmented table and index data in 8.0.3