Re: CREATE UNLOGGED TABLE seq faults when debug_discard_caches=1

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Geier <geidav(dot)pg(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, info(at)cspug(dot)cz
Subject: Re: CREATE UNLOGGED TABLE seq faults when debug_discard_caches=1
Date: 2022-11-18 14:53:53
Message-ID: 6b52e783-1b32-e723-4311-0e433a5a5a75@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/18/22 15:43, Tom Lane wrote:
> David Geier <geidav(dot)pg(at)gmail(dot)com> writes:
>> On a different note: are we frequently running our tests suites with
>> debug_discard_caches=1 enabled?
>> It doesn't seem like.
>
> Hmm. Buildfarm members avocet and trilobite are supposed to be
> doing that, but their runtimes of late put the lie to it.
> Configuration option got lost somewhere?
>

Yup, my bad - I forgot to tweak CPPFLAGS when upgrading the buildfarm
client to v12. Fixed, next run should be with

CPPFLAGS => '-DCLOBBER_CACHE_ALWAYS',

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-11-18 15:06:32 Re: Patch: Global Unique Index
Previous Message Tom Lane 2022-11-18 14:45:44 Re: Optimize join selectivity estimation by not reading MCV stats for unique join attributes