Is it good practice to index a large text column (up to 800KB) for full-text search in PostgreSQL?

I'm working on a PostgreSQL database for a blogging platform, and one of the columns in my table, blog_content, can hold text up to 800KB per row. This column stores the main content of blog posts, and I need to enable full-text search functionality on it.

To achieve this, I'm considering creating a GIN index on this column, using PostgreSQL's default tsvector approach. However, I'm concerned about potential performance issues and whether indexing such a large text column is a good practice.

Here are my specific concerns:

1. Index Size: How much storage overhead will this introduce, given the size of the column and the fact that there are millions of rows in the table?

2. Performance Impact: Will querying the index still be efficient for full-text search on such large text fields, or will the size of the index itself slow down queries? Alternatives: Are there better approaches for handling full-text search on large text columns like this?

Finally, is it common practice to index such large text columns directly in PostgreSQL, or should I consider restructuring my data or architecture?

Any advice on the pros and cons of indexing such a large text column for full-text search in PostgreSQL would be greatly appreciated!