Thanks for the reply.
I suspect there must have been some testing when the tsvector was created,
and I would be surprised if there is no general "how big is this object" method in PostgreSQL.
That said perhaps this is the wrong mailing list for this question.
If it's "bad design" to store large text documents (pdf,docx,etc) as a BLOBs or on a filesystem
and make them searchable with tsvectors can you suggest a good design?
If making your own search implementation is "better" what is the point of tsvectors?
Maybe I'm missing something here?
On Tue, Jun 14, 2011 at 10:18 AM, Kevin Grittner <Kevin.Grittner@xxxxxxxxxxxx> wrote:
Tim <elatllat@xxxxxxxxx> wrote:It would appear that nobody has run into this as a limit, nor done
> How many bytes of a tsvector would a 32MB ascii english unique
> word list make?
> How many bytes of a tsvector would something like "The Lord of the
> Rings.txt" make?
those specific tests. Storing a series of novels as a single value
in a database seems to be bad design, of course, which might explain
the lack of research.
If you get some numbers through testing, please post them for future
reference.
-Kevin
