Re: When Update balloons memory

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Klaudie Willis <Klaudie(dot)Willis(at)protonmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: When Update balloons memory
Date: 2022-01-11 19:59:12
Message-ID: CAH2-WzkLUqdY3DT-Mz85hbNyWhBFETUvHsZUZ1J7ZjQ-b=ZV7A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

On Tue, Jan 11, 2022 at 11:54 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Pass NULL for that, per 6867f963e:
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=6867f963e#patch2

Will look into that.

> We'd have to back-patch that bit, but I don't see any problem
> with doing so.

But the back-patch fix will make index_unchanged_by_update return true
unconditionally (to avoid an ABI break). It won't actually do anything
with Vars, which, as I said, seems okay given the current way in which
we apply the hint.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2022-01-11 21:15:34 Re: When Update balloons memory
Previous Message Tom Lane 2022-01-11 19:54:28 Re: When Update balloons memory

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2022-01-11 21:15:34 Re: When Update balloons memory
Previous Message Tom Lane 2022-01-11 19:54:28 Re: When Update balloons memory