http://archives.postgresql.org/
http://www.postgresql.org/search/?u=%2Fdocs%2F9.1%2F&q=c...
It's also handy because you can combine it with relational data. For example, if you search from a manual page of a particular version of Postgres, it'll only return results from that version.
The main performance limitation is probably update/insert rate, and it doesn't has as many features as a dedicated IR-type system, but it's frequently good-enough and already present.
I know CouchDB and MongoDB both make it pretty easy to add Solr/ElasticSearch into the equation.
Postgresql fulltext and ElasticSearch are ultimately solving two very different sorts of problems.
The only case I can think of where you would prefer to use PGSQL is if you some weird blending of normal relational data with the documents, but I think realistically you can sidestep that. We've been able to do pretty complicated queries against our ElasticSearch instances.
If you want to do full text searching of documents, probably PostgreSQL is not the right answer. If you want to pull all customers in the UK with notes searched full-text-wise for "did not pay" then PostgreSQL is much better just because it all integrates into the same filter.