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@xxxxxxxxxxxxx> wrote: > Aaron <aaron@xxxxxxxxxxxxxxx> 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 > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
