# Bugs #1831: PostgreSQL 8.1: index error when importing manual from egroupware.org

**URL:** <http://discourse.egroupware.org/t/bugs-1831-postgresql-8-1-index-error-when-importing-manual-from-egroupware-org/42858>\
**Category:** eGW-tracker\
**Created:** [December 3, 2010, 4:53pm UTC](http://discourse.egroupware.org/t/bugs-1831-postgresql-8-1-index-error-when-importing-manual-from-egroupware-org/42858 "2010-12-03T16:53:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tracker-3](http://discourse.egroupware.org/letter_avatar_proxy/v4/letter/t/d07c76/32.png) [@tracker-3](http://discourse.egroupware.org/u/tracker-3)\
**Post date:** [December 3, 2010, 4:53pm UTC](http://discourse.egroupware.org/t/bugs-1831-postgresql-8-1-index-error-when-importing-manual-from-egroupware-org/42858/1 "2010-12-03T16:53:14Z")

</div>

Ticket modified by Ralf Becker at 2010/12/03 23:53  
Tracking System: Bugs  
Category: Manual  
Version: Trunk

> Status: Pending  
> Resolution: Fixed  
> Completed: 0%  
> Priority: 5 - medium  
> Created By: Yudhi Kusnanto  
> Assigned to: Ralf Becker  
> Summary: #1831 - PostgreSQL 8.1: index error when importing manual from [egroupware.org](http://egroupware.org)  
> when i click admin-\>manual-\>import, processing stop with error when an entry contain large row. the message i reproduce is like this:  
> SQL error:

ERROR: index row size 3596 exceeds btree maximum, 2713  
HINT: Values larger than 1/3 of a buffer page cannot be indexed.  
Consider a function index of an MD5 hash of the value, or use full text indexing.

In statement:  
CREATE INDEX “egw\_wiki\_pages\_body” ON “egw\_wiki\_pages” USING BTREE (“wiki\_body”)

this index is new compare to 1.4.x.

after deleting and recreate the index using HASH, importing manual continue successfully.

## ADDITIONAL INFO: egw-trunk: rev. 26335 db: Postgresql 8.1 php: v5.1.x apache: v2.2x

> Comment by Ralf Becker at 2010/12/03 23:53:  
> Dear EGroupware user,

thanks for reporting bugs back to [egroupware.org](http://egroupware.org).

With the new release of EGroupware 1.8.001 we also fixed many bugs. So we kindly ask you to recheck your bug reports against the new version.

If you do not respond within the next 14 days, we assume the bug no longer exist and your report will be closed automatically.

Thanks for your understanding

## Ralf Becker Stylite GmbH

Comment by Yudhi Kusnanto at 2008/11/14 04:28:  
this bug is re-open because it’s still present on new installation using trunk rev.26364.

additional info:

eGroupWare API version 1.5.017 (svn trunk r.26364)  
Manual/Help version 1.6

## Error log is attached.

Comment by Ralf Becker at 2008/11/13 18:35:  
Hi,  
problem should be fixed with svn revision r26299 for newly created databases:  
[http://www.egroupware.org/viewvc?view=rev&revision=26299](http://www.egroupware.org/viewvc?view=rev&revision=26299)  
Before indexes were created for longtext column. Now we only create MySQL Fulltext indexes for text and longtext, and non for any other database.  
Please test again with a new install and re-open if the problem persists.  
Ralf

linked entries:  
[http://www.egroupware.org/egroupware/index.php?menuaction=tracker.tracker\_ui.edit&tr\_id=1831&no\_popup=1](http://www.egroupware.org/egroupware/index.php?menuaction=tracker.tracker_ui.edit&tr_id=1831&no_popup=1)