Euler Taveira de Oliveira <[EMAIL PROTECTED]> writes: > Edwin Groothuis wrote: >> Is it possible to make it a WARNING instead of an ERROR? Right now I get: >> > No. All of the other types emit an ERROR if you're trying an out of > range value.
I don't think that follows. A tsearch index is lossy anyway, so there's no hard and fast reason why it should reject entries that it can't index completely. I think it would be more useful to index whatever it can (probably just the words in the first N bytes of the document) than to prevent you from storing the document. There is another precedent too, namely that tsearch already discards individual words over so-many-bytes long. If it doesn't throw an error for that case, why is it throwing an error for this one? regards, tom lane -- Sent via pgsql-patches mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches