Re: failures on barnacle (CLOBBER_CACHE_RECURSIVELY) because of memory leaks - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: failures on barnacle (CLOBBER_CACHE_RECURSIVELY) because of memory leaks
Date
Msg-id 53E95E63.2030200@fuzzy.cz
Whole thread Raw
In response to Re: failures on barnacle (CLOBBER_CACHE_RECURSIVELY) because of memory leaks  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: failures on barnacle (CLOBBER_CACHE_RECURSIVELY) because of memory leaks
Next
From: Noah Misch
Date:
Subject: Re: Removing dependency to wsock32.lib when compiling code on WIndows