It fails when processing torrents that produce too large `tsvector`s.

[issuefiler]

• I have checked the existing issues to avoid duplicates
• I have redacted any info hashes and content metadata from any logs or screenshots attached to this issue

Describe the bug

The process_torrent job failed with the string is too long for tsvector error.

ERROR   queue   server/server.go:238    job failed      {"queue": "process_torrent", "error": "job failed to process: ERROR: string is too long for tsvector (1129652 bytes, max 1048575 bytes) (SQLSTATE 54000)"}

To reproduce

• Encounter a torrent that produces a rather large tsvector.

Expected behavior

Rather than failing it, it needs a fallback, such as generating a partial tsvector instead.

Environment

• bitmagnet version: 0.10.0-3-g4a45981.
• OS: Windows 11.

[issuefiler]

• The dht_crawler.save_files_threshold was 65536.
• Using PostgreSQL 17.
• It occurred for about a dozen torrents out of a few millions.
• It took several days of execution to run into this kind of job failures.