Lior,
* Ben Zeev, Lior (lior.ben-zeev@hp.com) wrote:
> Yes, The memory utilization per PostgreSQL backend process is when running queries against this tables,
> For example: select * from test where num=2 and c2='abc'
> When It start it doesn't consume to much memory,
> But as it execute against more and more indexes the memory consumption grows
It might be interesting, if possible for you, to recompile PG with
-DCATCACHE_FORCE_RELEASE, which should cause PG to immediately release
cached information when it's no longer being used. You'll be trading
memory usage for CPU cycles, of course, but it might be better for your
situation. We may still be able to do better than what we're doing
today, but I'm still suspicious that you're going to run into other
issues with having 500 indexes on a table anyway.
Thanks, Stephen
