| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
| Cc: | Jonathan Hedstrom <jhedstrom(at)desc(dot)org>, pgsql general <pgsql-general(at)postgresql(dot)org>, Ken Tanzer <ktanzer(at)desc(dot)org> |
| Subject: | Re: ERROR: invalid memory alloc request size, and others |
| Date: | 2007-01-09 21:24:05 |
| Message-ID: | 10523.1168377845@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Scott Marlowe <smarlowe(at)g2switchworks(dot)com> writes:
> On Tue, 2007-01-09 at 13:38, Jonathan Hedstrom wrote:
>> We recently upgraded from 8.1.4 to 8.2.0 on Fedora Core 6, and are now
>> seeing a few rather ominous-looking messages.
> First step, update to 8.2.1, it came out yesterday, and there were a few
> bugs that got stomped.
Definitely good advice, although none of these messages look related to
the known fixes.
> Also, schedule some maintenance window for your server to run memtest86
> and possibly something to check for bad blocks on your drives.
+1 ... I have not seen any instance of "invalid page header" that could
be traced to a Postgres bug. The cases I've been able to study all
seemed to involve either flaky hardware or kernel-level bugs (such as
dumping a fragment of some unrelated file into a Postgres table :-()
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-01-09 21:30:53 | Re: PGPASS.CONF ¿is there a way to p |
| Previous Message | guillermo arias | 2007-01-09 21:23:49 | PGPASS.CONF ¿is there a way to protect it? |