Daniele Bortoluzzi writes:
>> Can you still reproduce this with CVS HEAD,
> with CVS HEAD the error is not occurring. Did you fix some GIN bug in
> this version?
Yes, I told you so.
http://archives.postgresql.org/pgsql-committers/2009-06/msg00081.php
But I don't see how that bug would've led to
[...]
>Can you still reproduce this with CVS HEAD,
with CVS HEAD the error is not occurring. Did you fix some GIN bug in
this version?
Thank you for your support
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailp
Daniele Bortoluzzi writes:
> If I cannot reproduce the error, what is the best way to catch the
> stack trace? Do I have to recompile with --enable-debug?
Yes, that would be the best thing. If you are using gcc there is no
harm in using --enable-debug all the time; it just makes the executable
f
2009/6/10 Tom Lane :
[...]
> 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
"Daniele Bortoluzzi" 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
"Daniele Bortoluzzi" writes:
> Description:Database corruption after btree_gin index creation
Can you provide a self-contained test case to reproduce this problem?
We had a similar report yesterday but no one can reproduce it.
regards, tom lane
--
Sent via pgsql
The following bug has been logged online:
Bug reference: 4838
Logged by: Daniele Bortoluzzi
Email address: borto...@gmail.com
PostgreSQL version: 8.4beta2
Operating system: Linux amd64 2.6.24 (Debian 4.0)
Description:Database corruption after btree_gin index creation
