Closed
Bug 291803
Opened 20 years ago
Closed 19 years ago
PostgreSQL dies when you insert a string longer than 2700 characters into an indexed field
Categories
(Bugzilla :: Creating/Changing Bugs, defect, P1)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.20
People
(Reporter: mkanat, Assigned: mkanat)
References
()
Details
Attachments
(1 file)
(deleted),
patch
|
jouni
:
review+
|
Details | Diff | Splinter Review |
I was working on my MySQL-to-PostgreSQL script, and when it tried to copy
comments from the longdescs table in MySQL to the longdescs table in PostgreSQL,
I got:
DBD::Pg::st execute failed: ERROR: btree: index item size 2732 exceeds maximum 2713
The URL says that this is a problem with indexing, but I haven't looked into it
too deeply...
It's possible that we need to somehow limit our indexes on the thetext field.
Assignee | ||
Updated•20 years ago
|
Target Milestone: --- → Bugzilla 2.20
Assignee | ||
Updated•20 years ago
|
Blocks: 291776
Summary: PostgreSQL can sometimes throw an "index item" error → PostgreSQL can sometimes throw an "index item size" error
Assignee | ||
Comment 1•20 years ago
|
||
Removing the index from the "thetext" field fixes this problem.
I doubt that our really complex "LIKE" statement in Simple Search will use the
index, anyway, so we can probably just eliminate it until we have fulltext indexing.
Assignee | ||
Updated•20 years ago
|
Summary: PostgreSQL can sometimes throw an "index item size" error → PostgreSQL dies when you insert a string longer than 2700 characters into an indexed field
Assignee | ||
Comment 2•20 years ago
|
||
The solution that Tomas and I have decided on is to remove any index marked as
"FULLTEXT" and just not create it in Pg.
Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•20 years ago
|
Assignee: create-and-change → mkanat
Status: ASSIGNED → NEW
Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P1
Assignee | ||
Comment 3•20 years ago
|
||
OK, I think this is the simplest and cleanest solution for 2.20. It's a pretty
small patch, this way.
Attachment #183041 -
Flags: review?(bugzilla)
Assignee | ||
Updated•20 years ago
|
Attachment #183041 -
Flags: review?(bugzilla) → review?(bugreport)
Assignee | ||
Comment 4•20 years ago
|
||
Comment on attachment 183041 [details] [diff] [review]
Remove the "thetext" index and only create it on MySQL
Hey Jouni, could you review this? I haven't heard from Joel in a while.
Attachment #183041 -
Flags: review?(bugreport) → review?(jouni)
Comment 5•20 years ago
|
||
Comment on attachment 183041 [details] [diff] [review]
Remove the "thetext" index and only create it on MySQL
Works on MySQL, cannot test with Postgres. r=jouni, partially by inspection.
Attachment #183041 -
Flags: review?(jouni) → review+
Assignee | ||
Comment 6•20 years ago
|
||
OK, And I assert that I've tested this code on PostgreSQL, and it works.
Flags: approval?
Updated•19 years ago
|
Flags: approval? → approval+
Assignee | ||
Comment 7•19 years ago
|
||
Checking in checksetup.pl;
/cvsroot/mozilla/webtools/bugzilla/checksetup.pl,v <-- checksetup.pl
new revision: 1.403; previous revision: 1.402
done
Checking in Bugzilla/DB/Pg.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/DB/Pg.pm,v <-- Pg.pm
new revision: 1.10; previous revision: 1.9
done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•