postgres 8.1 crashing

From: Kari Lavikka <tuner(at)bdb(dot)fi>
To: pgsql-bugs(at)postgresql(dot)org
Subject: postgres 8.1 crashing
Date: 2005-11-29 16:42:14
Message-ID: Pine.HPX.4.62.0511291838590.2133@purple.bdb.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


my previous post just vanished...

Hi!

I just upgraded pg 8.0.3 to 8.1 (dump and reload) and outcome was a
corrupted database. pg 8.1 seemed to fly but backends were crashing :-/

While tailing the log file I noticed a couple of:
ERROR: invalid memory alloc request size 1101389186

Hardware is Sun v40z with 64bit Debian Sarge, Linux 2.6.13.2. Size of
database is somewhere around 500M rows and it's loaded by a website with a
lot of traffic.

Configuration:
http://tuner.bdb.fi/postgresql.conf

Some backtraces (update queries are included in the bt):
http://tuner.bdb.fi/pg_crashing.txt
http://tuner.bdb.fi/pg_crashing2.txt
http://tuner.bdb.fi/pg_crashing3.txt

And users-table which is involved in all the crashes is described
here (contains ~700000 rows):
http://tuner.bdb.fi/pg_crashing_table.txt

I tried to reindex the table but it didn't help. PG went corrupted
after a while:
http://tuner.bdb.fi/pg_crashing4.txt

Any ideas?

|\__/|
( oo ) Kari Lavikka - tuner(at)bdb(dot)fi - (050) 380 3808
__ooO( )Ooo_______ _____ ___ _ _ _ _ _ _ _
""

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Arjen van der Meijden 2005-11-29 16:43:17 Re: BUG #2075: Strange choice of bitmap-index-scan
Previous Message Tom Lane 2005-11-29 16:40:41 Re: pg_dump: schema with OID 559701082 does not exist