--
Paolo
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscribe@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAKFO%2Bx59T7ykkk9WT%3DoAyvG9xX-vxp4gSN0gLRAmSmz%2Byo1bqQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
I guess we'd also have the benefit of not having to keep elasticsearch running.
But I'm afraid I'm not familiar with Postgres. Is the FTS in Postgres mostly equivalent to ES, or will some kinds of search queries be affected?
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscribe@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ecd3a1ea-63d9-430c-af79-951022fec138%40googlegroups.com.
I'm pretty sure our search requirements on dp.com need that,
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1GFKbXyebkqmok_RYv3Hywq%3DfwXrfzXcgFxtZU7-Ez5%3DA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM2w90gRXxLwJ30Bz1sutQxM%3DFdZWpQgNcsmp5DemOSvFQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1Egq8xasdZ2eRxvX2Qb6mH7ygv2xcx0FmUXQyc4kjW5WA%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ecd3a1ea-63d9-430c-af79-951022fec138%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1GFKbXyebkqmok_RYv3Hywq%3DfwXrfzXcgFxtZU7-Ez5%3DA%40mail.gmail.com.
--Adam
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM2w90gRXxLwJ30Bz1sutQxM%3DFdZWpQgNcsmp5DemOSvFQ%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
On 7 May 2017, at 11:32, Curtis Maloney <cur...@tinbrain.net> wrote:Dogfooding is a fairly strong argument, IMHO.
Especially when there's a volunteer to do the work.
--
C
I agree that eliminating elasticsearch could be a simplification win from a maintenance perspective. For example, I spent some hours a few months ago debugging a problem with a new version of elasticsearch that caused our cluster to run out of memory and lock up every ~24 hours. Also, not having to set up elasticsearch to contribute to the docs.djangoproject.com search is nice. On the other hand, I wonder how moving the search load to PostgreSQL will effect server load, disk usage, etc.
On Monday, May 8, 2017 at 11:14:58 AM UTC-4, Tobias McNulty wrote:
I'm no FTS expert, but based just on the facts raised in this thread, if using Postgres FTSthat seems like a net win to me and as such at least worth exploring further. That is not to say I think we should commit to switching, but if we have volunteers who are excited to flesh out this proposal with some code and understand there's no guarantee it will actually get merged, I don't (yet) see a reason to say no.
- would not break existing nor potential search needs (in fact it might expand the functionality available) and
- would allow eliminating an entire service from the infrastructure
I'm going to start a personal branch with a PostgreSQL full-text search functionality for the djangoproject.com website.
I would to sprint on it during the next EuroPython 2017 in Rimini and I've added the Sprint proposal in the wiki:
https://wiki.python.org/moin/EuroPython2017/Sprints