From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | erob <erob(at)gthcfoundation(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #5937: initdb: FATAL error: could not open relation with OID 2608 |
Date: | 2011-03-22 14:51:38 |
Message-ID: | 1300805338-sup-6980@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Excerpts from Etienne Robillard's message of lun mar 21 12:29:01 -0300 2011:
> $ md5sum postgresql-8.4.7.tar.gz
> 4771d4ae4fd9e7e9b92c22253517508d postgresql-8.4.7.tar.gz
>
> The detached MD5 signature matches the tarball I used for compiling
> postgresql server so I don't think
> its necessary to try downloading another. Maybe this is strictly a 8.4.x
> issue but will need to verify
> by downgrading to 8.3.x...
8.4.x has been tested by hundreds of machines. I build it here on a
Debian machine at least once a week and I have never seen this problem.
I don't think it's a generic PG problem; maybe there's something wrong
with your machine or setup. Have you tested the hardware? Is the
error reproducible exactly in the same way every time? (if not, it might
suggest a hardware problem -- did you try memtest86?). If it's not a
hardware problem, how did you compile it?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Matthijs Bomhoff | 2011-03-22 15:31:47 | Bug with STABLE function using the wrong snapshot (probably during planning) |
Previous Message | Jonathan Brinkman | 2011-03-22 12:56:47 | Re: TO_CHAR(timestamptz,datetimeformat) wrong after DST change |