Hi! On 30.03.2026 18:26, Matthias van de Meent wrote:
So, I think the attached patch is a more appropriate fix, it avoids calling into ExecInitGenerated at all when no column included in expressions was updated. It also adds an assertion that the function isn't called again once the field has been initialized. It also has the benefit of being backportable.
Agreed that this "one floor higher" fix is rather simpler and much more native than my variant with caching. Thanks a lot for reply! Best regards, -- Anton A. Melnikov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
