Bruce Momjian wrote:
I have updated the FAQ to handle three of the items you mentioned. In
one case, I added a new FAQ entry (double-quoting identifiers with a
link to our docs), and in two other cases (indexing long columns,
case-insensitive columns) I added to existing FAQ items where
appropriate. Patch attached and applied.
For the batch job and single-CPU issues, they did not fit into existing
FAQ entries, and I am not sure they are asked enough to be added as
FAQs. I am interested to hear other's opinions on this.
***************
*** 613,618 ****
--- 617,628 ----
<P>The maximum table size and maximum number of columns can be
quadrupled by increasing the default block size to 32k.</P>
+ <P>One limitation is that indexes can not be created on columns
+ longer than about 2,000 characters. Fortunately, such indexes are
+ rarely needed. Uniqueness is best guaranteed using another column
+ that is an MD5 hash of the long column, and full text indexing
+ allows for searching of words within the column.</P>
+
<H3><A name="4.5">4.5</A>) How much database disk space is required
to store data from a typical text file?</H3>
I liked the FAQ entry written up by the original submitter much better,
WRT to the long index issue. This write up does not contain the actual
error message encountered, so its not going to be found by someone
looking for a solution to the problem. It doesn't contain the optional
workaround, and it doesn't have a link into the full text searching
features as the recommended fix. I was one of the more recent people
to encounter this problem, and I don't think that this FAQ would have
helped me (if I even saw it, because google certainly won't pick it up
in a way that most people will search when the encounter the issue -
they are going to put in the error message)
Dan
--
****************************
Daniel Armbrust
Biomedical Informatics
Mayo Clinic Rochester
daniel.armbrust(at)mayo.edu
http://informatics.mayo.edu/
|
