Re: failures on barnacle (CLOBBER_CACHE_RECURSIVELY) because of memory leaks

From: Tomas Vondra <tv(at)fuzzy(dot)cz>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: failures on barnacle (CLOBBER_CACHE_RECURSIVELY) because of memory leaks
Date: 2014-08-12 00:22:59
Message-ID: 53E95E63.2030200@fuzzy.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12.8.2014 02:05, Tom Lane wrote:
>
> Evidently the OOM killer is at large on this machine.

Yes. It's a machine with only 8GB of RAM, and there are 3 VMs (LXC
containers), with 2GB of RAM each. That's not much, but while it's
mostly out of necessity, it's apparently a good way to catch leaks.

Tomas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2014-08-12 00:43:44 Re: Removing dependency to wsock32.lib when compiling code on WIndows
Previous Message Tom Lane 2014-08-12 00:05:57 Re: failures on barnacle (CLOBBER_CACHE_RECURSIVELY) because of memory leaks