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

2014-08-24 Thread Tomas Vondra
On 24.8.2014 18:28, Tom Lane wrote: > Tomas Vondra writes: >> Regarding those leaks we've detected so far - is it the kind of leaks >> that can happen only in testing with those specific flags, or is it >> something that can happen in production too? (Assuming no one is running >> with CLOBBER_CAC

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

2014-08-24 Thread Tom Lane
Tomas Vondra writes: > Regarding those leaks we've detected so far - is it the kind of leaks > that can happen only in testing with those specific flags, or is it > something that can happen in production too? (Assuming no one is running > with CLOBBER_CACHE_RECURSIVELY in production, of course ;-

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

2014-08-24 Thread Tomas Vondra
On 24.8.2014 18:01, Tom Lane wrote: > Tomas Vondra writes: >>> I stopped the already running test on addax and started the test on >>> barnacle again. Let's see in a few days/weeks/months what is the result. > >> It seems to be running much faster (probably after removing the >> randomization), a

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

2014-08-24 Thread Tom Lane
Tomas Vondra writes: >> I stopped the already running test on addax and started the test on >> barnacle again. Let's see in a few days/weeks/months what is the result. > It seems to be running much faster (probably after removing the > randomization), and apparently it passed the create_view test

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

2014-08-20 Thread Tomas Vondra
Hi, On 13.8.2014 19:17, Tomas Vondra wrote: > On 13.8.2014 17:52, Tom Lane wrote: > >> * I'm a bit dubious about testing -DRANDOMIZE_ALLOCATED_MEMORY in the >> same build as -DCLOBBER_CACHE_RECURSIVELY, because each of these is >> darned expensive and it's not clear you'd learn anything by running

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

2014-08-13 Thread Tomas Vondra
On 13.8.2014 17:52, Tom Lane wrote: > "Tomas Vondra" writes: >> So after 83 days, the regression tests on barnacle completed, and it >> smells like another memory leak in CacheMemoryContext, similar to those >> fixed in 078b2ed on May 18. > > I've pushed fixes for the issues I was able to identif

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

2014-08-13 Thread Tom Lane
"Tomas Vondra" writes: > So after 83 days, the regression tests on barnacle completed, and it > smells like another memory leak in CacheMemoryContext, similar to those > fixed in 078b2ed on May 18. I've pushed fixes for the issues I was able to identify by running the create_view test. I definit

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

2014-08-12 Thread Tom Lane
I wrote: > "Tomas Vondra" writes: >> So after 83 days, the regression tests on barnacle completed, > Hah, that's perseverance! >> and it >> smells like another memory leak in CacheMemoryContext, similar to those >> fixed in 078b2ed on May 18. > Ugh, will look. I've been experimenting by runnin

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

2014-08-11 Thread Tomas Vondra
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. T

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

2014-08-11 Thread Tom Lane
"Tomas Vondra" writes: > So after 83 days, the regression tests on barnacle completed, Hah, that's perseverance! > and it > smells like another memory leak in CacheMemoryContext, similar to those > fixed in 078b2ed on May 18. Ugh, will look. > See this: > http://pgbuildfarm.org/cgi-bin/show_lo