From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Felde Norbert <fenor77(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Subject: | Re: postgres crash SOS |
Date: | 2010-06-17 14:39:00 |
Message-ID: | AANLkTinr8iSM-6GmlJFVrbP3StBSsYo__E-C_oQJEdj7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jun 17, 2010 at 10:35 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Thu, Jun 17, 2010 at 4:47 AM, Felde Norbert <fenor77(at)gmail(dot)com> wrote:
>> Before I began I made a filesystem level backup after I stopped the
>> postgres service.
>> I have the original 0003 file, the size is 204800, The size of the
>> other files in this dir is 262144.
>
> hm...any indication of why the file is small? run out of space?
> filesystem/os issues?
>
> try appending hex 0x55 to the end of the file until it's the right
> length and starting up the database. disable everything (don't vacuum)
> and immediately try to pull off a dump.
>
> what's the last good backup you have?
if you want to move this along faster and get some more minds on the
problem, hop onto postgresql irc channel:
http://www.postgresql.org/community/irc
also make sure not to modifiy your original filesystem snapshot.
always modify the copy first.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas | 2010-06-17 15:12:36 | weird sortorder issue |
Previous Message | Merlin Moncure | 2010-06-17 14:35:26 | Re: postgres crash SOS |