Re: Avoid calling SetMatViewPopulatedState if possible

From: David Geier <geidav(dot)pg(at)gmail(dot)com>
To: cca5507 <cca5507(at)qq(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Avoid calling SetMatViewPopulatedState if possible
Date: 2026-05-04 18:29:47
Message-ID: 4172933b-dc7c-4fce-8ea1-154cf4864511@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 10.04.2026 05:36, cca5507 wrote:
> During refresh matview, we call SetMatViewPopulatedState unconditionally even
> if the value doesn't change. Attach a small patch to optimize it.

Thanks for sharing this patch.

While being a simple patch, it would be good to know what actual use
cases this change improves on and by how much. Can you share a test case
and/or performance data?

--
David Geier

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-05-04 19:22:37 Re: Serverside SNI support in libpq
Previous Message SATYANARAYANA NARLAPURAM 2026-05-04 18:08:06 Re: [Bug]Vacuum full silently NULL out fast default columns