From: | Aaron <aaron(at)chasingnuts(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: GiST or GIN, I feel like I am doing something wrong |
Date: | 2009-06-17 17:16:24 |
Message-ID: | 13e03a2b0906171016i3ed36ca0r4db4ca27ec10f712@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom,
Our maintenance_work_mem is 1024MB so there should have been plenty of
memory for INDEX creation. I happened to be watching top when we
created the GiN INDEX and the process used about 500MB of non-shared
memory.
Aaron Thul
http://www.chasingnuts.com
On Wed, Jun 17, 2009 at 11:30 AM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Aaron <aaron(at)chasingnuts(dot)com> writes:
>> CREATE INDEX profile_images_fulltext_gin ON profile_images_fulltext
>> USING gin(content);
>> CREATE INDEX profile_images_fulltext_gist ON profile_images_fulltext
>> USING gist(content);
>
> What did you have maintenance_work_mem set to while you did this?
> GIST doesn't care, but GIN likes to have lots of workspace while
> building an index. I'm not entirely sure if small workspace only
> affects build time, or if it could result in a bloated/inefficient
> index ... but if the latter is true it might explain your results.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Whit Armstrong | 2009-06-17 18:16:33 | Re: how to cancel a query in progress |
Previous Message | Steve Atkins | 2009-06-17 16:10:36 | Re: used for large media files |