Re: question about PANIC: hash table "Shared Buffer Lookup Table" corrupted

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "bh yuan" <bhyuan(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: question about PANIC: hash table "Shared Buffer Lookup Table" corrupted
Date: 2008-02-05 04:10:39
Message-ID: 12853.1202184639@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"bh yuan" <bhyuan(at)gmail(dot)com> writes:
> I use Postgresql 7.4.19 wiht 8G memory on Redhat5 x86_64.
> And I modify the postgresql.conf file,
> when I set
> shared_buffers = 786432 # min 16, at least

7.4 does not support more than 2Gb (or maybe 4Gb, I forget) of shared
memory. Furthermore, it so little imagines that you might want that
much that it doesn't even guard itself against overflow. This is not
really a problem because its buffer management algorithms are not good
enough to support more than a few tens of thousands of shared buffers
anyway.

In short: don't do that.

Modern versions of PG (say, 8.1 or later) are somewhat competent with
large amounts of shared buffers.

Why are you even trying such an obsolete version of PG on RHEL5?
What Red Hat ships in RHEL5 is 8.1, and even that is pretty old in
the view of most people on this list.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ken Johanson 2008-02-05 04:24:09 failed to build any 8-way joins: SQLSTATE: XX000 on PostgreSQL 8.2.6
Previous Message Patrick TJ McPhee 2008-02-05 03:59:33 Re: [OT] "advanced" database design (long)