From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Tomas Vondra <tv(at)fuzzy(dot)cz>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: buildfarm: strange OOM failures on markhor (running CLOBBER_CACHE_RECURSIVELY) |
Date: | 2014-05-19 22:50:34 |
Message-ID: | 22788.1400539834@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-05-19 23:40:32 +0200, Tomas Vondra wrote:
>> I was however wondering if this might be related to OOM errors a few
>> local users reported to us. IIRC they've been using temporary tables
>> quite heavily - not sure if that could be related.
> I've significant doubts that it is.
The main leak (the whole-Relation one) only applies to entries for certain
system catalogs. The smaller leak would apply to any relation having
DEFAULT column values --- but it's fairly hard to see how any table would
get invalidated so many times in one query as to make that leak an issue,
unless you were doing CLOBBER_CACHE or similar stress testing.
> I suggest you disable memory overcommit - then you'll get nice memory
> dumps on stderr instead of oom kills.
Yeah, a context stats dump would help a lot here.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2014-05-19 23:58:56 | Re: buildfarm animals and 'snapshot too old' |
Previous Message | Thomas Munro | 2014-05-19 22:24:14 | Re: SKIP LOCKED DATA (work in progress) |