| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: buildfarm: strange OOM failures on markhor (running CLOBBER_CACHE_RECURSIVELY) |
| Date: | 2014-05-19 21:48:42 |
| Message-ID: | 20140519214842.GG11150@alap3.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-05-19 23:40:32 +0200, Tomas Vondra wrote:
> On 19.5.2014 22:11, Tom Lane wrote:
> > Tomas Vondra <tv(at)fuzzy(dot)cz> writes:
> > I intentionally didn't do that, first because I have only a limited
> > amount of confidence in the patch, and second because I don't think
> > it matters for anything except CLOBBER_CACHE_RECURSIVELY testing.
> > Which surely you're not going to do in the back branches?
>
> Yes, I'm running this on HEAD only.
>
> 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. I suggest you disable memory
overcommit - then you'll get nice memory dumps on stderr instead of oom
kills.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2014-05-19 22:24:14 | Re: SKIP LOCKED DATA (work in progress) |
| Previous Message | Tomas Vondra | 2014-05-19 21:40:32 | Re: buildfarm: strange OOM failures on markhor (running CLOBBER_CACHE_RECURSIVELY) |