Re: CREATE UNLOGGED TABLE seq faults when debug_discard_caches=1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 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:43:55
Message-ID: 2185210.1668782635@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

prion is running with -DRELCACHE_FORCE_RELEASE -DCATCACHE_FORCE_RELEASE,
which I would have thought would be enough to catch this, but I guess
not.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-11-18 14:45:44 Re: Optimize join selectivity estimation by not reading MCV stats for unique join attributes
Previous Message Andrew Dunstan 2022-11-18 13:50:47 Re: Fix proposal for comparaison bugs in PostgreSQL::Version