News for hackers. Stuff that matters.
Re:Full-Text Search in Django with PostgreSQL by holmberd on Saturday January 06, 2018 @12:54PM (#16086488)
Having implemented this for a client in the past I have to agree that it is a cheaper option than ElasticSearch, especially for smaller projects with a lower number of records to index.

ElastiSearch easily gets expensive and the search suggestion is pretty bad.

Re:Full-Text Search in Django with PostgreSQL by threeseed on Saturday January 06, 2018 @02:20PM (#16086943)
What does this mean ?

ElasticSearch starts off as a small Java application that wraps the Lucene library.

Obviously heap will increase with usage and number of documents but I am still confused how it is in any way "expensive".

Re:Full-Text Search in Django with PostgreSQL by pauloxnet on Saturday January 06, 2018 @07:50PM (#16088401)
The stack I proposed in my article is pretty simple: Django + PostgreSQL (DB + FTS).

In other project I used Elastic for the search function: Django + PostgreSQL (DB) + Haystack + ES (FTS).

Is obvious that the second solution is more expensive.

Re:Full-Text Search in Django with PostgreSQL by pauloxnet on Saturday January 06, 2018 @01:09PM (#16086585)
Thanks for your feedback, I obviously agree with you, but I'm starting to plan to use PG FTS with Django also in some bigger project. I hope to write another article about it in new future.
Re:Full-Text Search in Django with PostgreSQL by holmberd on Saturday January 06, 2018 @01:37PM (#16086726)
Depends on the data right. I've seen good performance on larger tables after using GIN indexing with records that rarely needs to be updated and simple queries. I'm not a expert in PostgreSQL by any means, but reducing cost and learning something never hurts.
Re:Full-Text Search in Django with PostgreSQL by pauloxnet on Saturday January 06, 2018 @02:16PM (#16086928)
I totally agree with you