[...]
>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
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
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
