Re: Debugging shared memory issues on CentOS

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Mack Talcott <mack(dot)talcott(at)gmail(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Debugging shared memory issues on CentOS
Date: 2013-12-12 15:17:08
Message-ID: 3931.1386861428@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> It's tempting to say, "there should be a limit to backend local cache"
> but it's not clear if the extra tracking is really worth it all things
> considered. There was some discussion about this (see the archives).

Yeah --- there actually was a limit on total catcache size once, long ago.
We took it out because it was (a) expensive to enforce and (b) either
pointless or counterproductive on most workloads. The catcache is
probably the least of the memory hogs anyway, so it might be that limiting
the size of relcache or function caches would be more useful. But that
memory is likely to discourage most hackers from investigating.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Sev Zaslavsky 2013-12-12 17:30:10 slow query - will CLUSTER help?
Previous Message Merlin Moncure 2013-12-12 14:56:59 Re: Debugging shared memory issues on CentOS