| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Daniele Bortoluzzi" <bortoluz(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #4838: Database corruption after btree_gin index creation |
| Date: | 2009-06-10 01:44:03 |
| Message-ID: | 4051.1244598243@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Daniele Bortoluzzi" <bortoluz(at)gmail(dot)com> writes:
> I created a multicolumn GIN index with btree_gin functionality (fulltext
> column + timestamp). After creating the index the db segfaulted:
> LOG: server process (PID 14195) was terminated by signal 11: Segmentation
> fault
I cannot replicate this problem based on the little information
provided. The GIN bug we found a couple of days ago would explain
the "tuple offset out of range" errors, and if you had had Asserts
enabled it would explain Assert failures; but I don't see that it
explains a segfault. Can you still reproduce this with CVS HEAD,
and if so would you submit a test case? Or at least a stack trace
from the crash?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Burladyan | 2009-06-10 01:49:02 | pg 8.3.7 libxml trying to free NULL pointer |
| Previous Message | Peter Eisentraut | 2009-06-09 22:06:39 | Re: [HACKERS] BUG #4822: xmlattributes encodes '&' twice |