| From: | Mark <Marek(dot)Balgar(at)seznam(dot)cz> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: GIN index not used |
| Date: | 2011-04-30 18:37:18 |
| Message-ID: | 1304188638836-4361529.post@n5.nabble.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alban thank for your ideas
> It probably is, the default Postgres settings are quite modest and GIN
> indexes are memory hungry.
> I think you need to increase shared_buffers. With 2.5GB of memory (such a
> strange number) the docs > suggest about 250MB.
> See
> http://www.postgresql.org/docs/current/static/runtime-config-resource.html
> for details.
Well I did not mentioned that it all runs on Virtual Machine so that's why
2.5GB. I could not assigned more.
Today I have tried the VM machine on PC where I assigned 9GB of memory to
this VM. There I set the shared_buffers on 900MB. You were right it wa's
definitely caused by the size of memory.
I do not understand why before it was such quick even, if I had less memory.
Thanks very much for your help :-)--
View this message in context: http://postgresql.1045698.n5.nabble.com/GIN-index-not-used-tp4344826p4361529.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2011-04-30 18:55:09 | Re: Huge spikes in number of connections doing "PARSE" |
| Previous Message | Rob Sargent | 2011-04-30 18:14:37 | Re: histogram |