I'm no FTS expert, but based just on the facts raised in this thread, if using Postgres FTS
1. would not break existing nor potential search needs (in fact it might expand the functionality available) and 2. would allow eliminating an entire service from the infrastructure that 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. Tobias *Tobias McNulty*Chief Executive Officer tob...@caktusgroup.com www.caktusgroup.com On Mon, May 8, 2017 at 10:07 AM, Marc Tamlyn <marc.tam...@gmail.com> wrote: > Yes, don't need that sorry. > > On 8 May 2017 at 14:40, Adam Johnson <m...@adamj.eu> wrote: > >> I'm pretty sure our search requirements on dp.com need that, >> >> >> s/need/don't need/ ? 😉 >> >> On 8 May 2017 at 13:59, Marc Tamlyn <marc.tam...@gmail.com> wrote: >> >>> I'm not sure I see the benefit here. The strength and purpose of >>> postgres FTS is that you can combine some FTS behaviour with some >>> relational queries easily at the same time. I'm pretty sure our search >>> requirements on dp.com need that, so using a dedicated search provider >>> is a better option. >>> >>> On 7 May 2017 at 13:22, Florian Apolloner <f.apollo...@gmail.com> wrote: >>> >>>> On Sunday, May 7, 2017 at 12:45:27 PM UTC+2, Adam Johnson wrote: >>>>> >>>>> I guess we'd also have the benefit of not having to keep elasticsearch >>>>> running. >>>>> >>>> >>>> On the contrary, putting it into postgres means we have to care about >>>> it. Putting it into Elasticsearch means we can let our hoster take care >>>> about that. >>>> >>>> >>>>> 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? >>>>> >>>> >>>> For the queries we use I think we can get pretty much equivalent >>>> results. >>>> >>>> -- >>>> 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+unsubscr...@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/ms >>>> gid/django-developers/ecd3a1ea-63d9-430c-af79-951022fec138%4 >>>> 0googlegroups.com >>>> <https://groups.google.com/d/msgid/django-developers/ecd3a1ea-63d9-430c-af79-951022fec138%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> 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+unsubscr...@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/ms >>> gid/django-developers/CAMwjO1GFKbXyebkqmok_RYv3Hywq%3DfwXrfz >>> XcgFxtZU7-Ez5%3DA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/django-developers/CAMwjO1GFKbXyebkqmok_RYv3Hywq%3DfwXrfzXcgFxtZU7-Ez5%3DA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> 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-developers+unsubscr...@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/ms >> gid/django-developers/CAMyDDM2w90gRXxLwJ30Bz1sutQxM%3DFdZWpQ >> gNcsmp5DemOSvFQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/django-developers/CAMyDDM2w90gRXxLwJ30Bz1sutQxM%3DFdZWpQgNcsmp5DemOSvFQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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+unsubscr...@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/CAMwjO1Egq8xasdZ2eRxvX2Qb6mH7y > gv2xcx0FmUXQyc4kjW5WA%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAMwjO1Egq8xasdZ2eRxvX2Qb6mH7ygv2xcx0FmUXQyc4kjW5WA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@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/CAMGFDKTBmKALZ5Ebm0zFBqNa-irn_Axz-ozpPqjZh2focT9Nag%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
