Re: multicolumn index and setting effective_cache_size using human-readable-numbers - Mailing list pgsql-general

From Geoff Winkless
Subject Re: multicolumn index and setting effective_cache_size using human-readable-numbers
Date
Msg-id CAEzk6ffejSAX0=NiyCPemu_8x9ErvF9ktjT38ozd+cHVeGs01g@mail.gmail.com
Whole thread Raw
In response to Re: multicolumn index and setting effective_cache_size using human-readable-numbers  (Geoff Winkless <pgsqladmin@geoff.dj>)
Responses Re: multicolumn index and setting effective_cache_size using human-readable-numbers  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-general
Just as a continuation of this, I can set effective_cache_size to 64MB
and it will still use the single-column index, but PG flatly refuses
to use the multicolumn index without effective_cache_size being an
unfeasibly large number (2x the RAM in the machine, in this case).

Geoff


pgsql-general by date:

Previous
From: Rémi Cura
Date:
Subject: bloated postgres data folder, clean up
Next
From: Alvaro Herrera
Date:
Subject: Re: Only owners can ANALYZE tables...seems overly restrictive