Re: Let plan_cache_mode to be a little less strict

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: Sami Imseih <samimseih(at)gmail(dot)com>, Andy Fan <zhihuifan1213(at)163(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Let plan_cache_mode to be a little less strict
Date: 2025-08-04 04:23:26
Message-ID: aJA1votIsIHkQHSL@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 01, 2025 at 03:07:08PM +0200, Andrei Lepikhov wrote:
> I considered the worker_spi.c module, which demonstrates various SPI usage
> patterns. It might be more beneficial to use this instead of creating
> another test module, isn't it?

worker_spi is a playground for bgworker tests, so I'm not eager to
make it more complex for the case of cached planned. SQL tests have
more benefits here, IMO, and they should be more efficient and more
predictible. worker_spi can only work with TAP.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2025-08-04 04:33:06 Re: A little cosmetic to convert_VALUES_to_ANY()
Previous Message Michael Paquier 2025-08-04 04:19:46 Re: [PATCH] Proposal to Enable/Disable Index using ALTER INDEX