From: Michael Paquier <michael@paquier.xyz>
To: David Rowley <dgrowleyml@gmail.com>
Cc: David Rowley <drowley@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Flush Memoize cache when non-key parameters change
Date: Wed, 24 Nov 2021 13:31:15 +0900
Message-ID: <YZ3AE1QC+ln3GQNK@paquier.xyz> (raw)
In-Reply-To: <CAApHDvoLFddJhLOZ3fNmhU5poEJzx-SCyGE5_YRjPZTrM2AosQ@mail.gmail.com>
References: <E1mphXS-0002Qq-2l@gemulon.postgresql.org>
<CAApHDvoLFddJhLOZ3fNmhU5poEJzx-SCyGE5_YRjPZTrM2AosQ@mail.gmail.com>
On Wed, Nov 24, 2021 at 03:18:53PM +1300, David Rowley wrote:
> I'm currently looking into why the buildfarm does not like this.
From what I can see, there are two separate problems here:
- force_parallel_mode = regress.
- -DRELCACHE_FORCE_RELEASE and/or -DCATCACHE_FORCE_RELEASE.
Regards,
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: michael@paquier.xyz, dgrowleyml@gmail.com, drowley@postgresql.org
Subject: Re: pgsql: Flush Memoize cache when non-key parameters change
In-Reply-To: <YZ3AE1QC+ln3GQNK@paquier.xyz>
References: <E1mphXS-0002Qq-2l@gemulon.postgresql.org> <CAApHDvoLFddJhLOZ3fNmhU5poEJzx-SCyGE5_YRjPZTrM2AosQ@mail.gmail.com> <YZ3AE1QC+ln3GQNK@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox