From: | Cory Nemelka <cnemelka(at)gmail(dot)com> |
---|---|
To: | Michael Lewis <mlewis(at)entrata(dot)com> |
Cc: | Jimmy Huang <jimmy_huang(at)live(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg full text search very slow for Chinese characters |
Date: | 2019-09-10 16:13:02 |
Message-ID: | CAMe5Gn2n3qYTCFf9Qb6QFg3ShgkoJ3nmkHkr40Mp=PjcEXS4yA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 10, 2019 at 10:11 AM Michael Lewis <mlewis(at)entrata(dot)com> wrote:
> >My postgres instance is based on docker image postgres:11 and runs on my
> MacBook Pro i7 16GB.
>
> How much ram and such did you give to this vm?
>
>
> >To my surprise, postgres 11 is extremely slow when creating a full text
> index. I added a column of tsvector type and tried to create an index on
> that column. Pg could not finish creating a GIN index for a long time and I
> had to cancel the execution.I then tried to create a partial full text
> index for 500 rows and it took postgres 2 to 3 minutes to create the index.
>
>
> Did you customize any config? maintenance_work_mem specifically would be
> relevant to the time to create an index and default value is only 64MB.
> Especially if you are running a spinning hard drive and not ssd, then this
> could be problematic.
>
I apologize for my top post. :D Won't happen again
From | Date | Subject | |
---|---|---|---|
Next Message | Jimmy Huang | 2019-09-10 16:20:57 | Re: pg full text search very slow for Chinese characters |
Previous Message | Michael Lewis | 2019-09-10 16:10:54 | Re: pg full text search very slow for Chinese characters |