Re: -DCLOBBER_CACHE_ALWAYS build takes far longer than before

From: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers list" <pgsql-hackers(at)postgresql(dot)org>, ohp(at)pyrenet(dot)fr
Subject: Re: -DCLOBBER_CACHE_ALWAYS build takes far longer than before
Date: 2008-04-20 16:32:11
Message-ID: 1d4e0c10804200932u2ebc1db6x6246311d08661f35@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 20, 2008 at 6:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It's probably due to the RANDOMIZE_ALLOCATED_MEMORY overhead added here:
>
> > pgsql/src/backend/utils/mmgr/aset.c 1.77
>
> Right now that's on by default in assert-enabled builds. I'm not
> sure if we want to leave it like that for long ...

OK. It's not a problem by itself. I just wanted to point it out.

Thanks.

--
Guillaume

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Mielke 2008-04-20 16:59:35 INSERT ... SELECT ... FOR SHARED?
Previous Message Tom Lane 2008-04-20 16:02:13 Re: -DCLOBBER_CACHE_ALWAYS build takes far longer than before