Re: postgres dumps core - HASH indexes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adam PAPAI <wooh(at)wooh(dot)hu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: postgres dumps core - HASH indexes
Date: 2007-11-18 19:51:02
Message-ID: 7615.1195415462@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Adam PAPAI <wooh(at)wooh(dot)hu> writes:
> After a few minutes, my postgres dumps core.
> (gdb) where
> #0 0x041ee52d in kill () from /usr/lib/libc.so.40.3
> #1 0x04226c37 in abort () at /usr/src/lib/libc/stdlib/abort.c:65
> #2 0x1c1c2fcb in errfinish ()
> #3 0x1c1c3be1 in elog_finish ()
> #4 0x1c040598 in _hash_expandtable ()

> Server/Client: 8.2.3

This is probably the same bug fixed in 8.2.4:

* Fix PANIC during enlargement of a hash index (Tom)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeremy Drake 2007-11-18 20:36:54 Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not
Previous Message Adam PAPAI 2007-11-18 19:45:20 postgres dumps core - HASH indexes