| From: | "Anton A(dot) Melnikov" <a(dot)melnikov(at)postgrespro(dot)ru> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [BUG] Excessive memory usage with update on STORED generated columns. |
| Date: | 2026-03-30 16:19:41 |
| Message-ID: | 420a2def-969d-4161-bacf-17e9b7a79562@postgrespro.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2026-03-30 16:23:43 | Re: Add GoAway protocol message for graceful but fast server shutdown/switchover |
| Previous Message | Álvaro Herrera | 2026-03-30 16:14:27 | Re: clang bug affecting greenfly |