Hi all.
Thanks for your feedbacks about my propose to use PostgrSQL FTS in
djangoproject.com
After my talk about "Full-Text Search with PostgreSQL in Django" in the
EuroPython 2017 I organized a sprint to work on a new branch of
djangoproject.com as I proposed.
https://twitter.com/i/moments/88631
> On 11 Jul 2017, at 12:49, Jannis Leidel wrote:
>
>> On 12. May 2017, at 11:42, Aymeric Augustin
>> wrote:
>>
>> These features are desirable and easy to configure with ES, but that wasn't
>> done, perhaps for lack of familiarity with ES.
>
> It was not out of lack of familiarity with ES bu
> On 12. May 2017, at 11:42, Aymeric Augustin
> wrote:
>
>> On 7 May 2017, at 11:32, Curtis Maloney wrote:
>>
>> Dogfooding is a fairly strong argument, IMHO.
>>
>> Especially when there's a volunteer to do the work.
>>
>> --
>> C
>
> I agree.
>
> I was mildly concerned about the effect o
Hi all,
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
I
> On 7 May 2017, at 11:32, Curtis Maloney wrote:
>
> Dogfooding is a fairly strong argument, IMHO.
>
> Especially when there's a volunteer to do the work.
>
> --
> C
I agree.
I was mildly concerned about the effect on relevance, but the current search
isn't all that good.
A quick test shows
Dogfooding is a fairly strong argument, IMHO.
Especially when there's a volunteer to do the work.
--
C
On 7 May 2017 6:53:13 PM AEST, Paolo Melchiorre wrote:
>On Sun, May 7, 2017 at 9:16 AM, Florian Apolloner
> wrote:
>> On Sunday, May 7, 2017 at 12:50:02 AM UTC+2, Paolo Melchiorre wrote:
>>>
>
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
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 lik
Yes, don't need that sorry.
On 8 May 2017 at 14:40, Adam Johnson 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 wrote:
>
>> I'm not sure I see the benefit here. The strength and purpose of postgres
>> F
>
> 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 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
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
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 a
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?
On 7 May 2017 at 09:53, Paolo Melchiorre wrote:
> On Sun, May 7, 2017
On Sun, May 7, 2017 at 9:16 AM, Florian Apolloner wrote:
> On Sunday, May 7, 2017 at 12:50:02 AM UTC+2, Paolo Melchiorre wrote:
>>
>> Hello,
>>
>> in the djangoproject.com the search is powered by elasticsearch.
>>
>> Since the site uses postgresql as database backend I want propose to use
>> the
What would be the benefit of using django.contrib.postgresql aside from
much work?
On Sunday, May 7, 2017 at 12:50:02 AM UTC+2, Paolo Melchiorre wrote:
>
> Hello,
>
> in the djangoproject.com the search is powered by elasticsearch.
>
> Since the site uses postgresql as database backend I want pro
Hello,
in the djangoproject.com the search is powered by elasticsearch.
Since the site uses postgresql as database backend I want propose to use
the Full-Text Search function provided by django.contrib.postgres.search
module.
I presented a talk "Full-Text Search in Django with PostgreSQL" at t
16 matches
Mail list logo
