Re: When Update balloons memory
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Klaudie Willis <Klaudie.Willis@protonmail.com>,
PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2021-12-14T23:28:52Z
Lists: pgsql-bugs, pgsql-general
Peter Geoghegan <pg@bowt.ie> writes: > On Tue, Dec 14, 2021 at 11:33 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> And, not to be too picky, but does this cope with the case where >> an indexed column is changed by a BEFORE trigger, not by the >> query proper? > No. It's much better to err in the direction of giving the hint, > rather than not giving the hint. In order for us to make the category > of error that seems like it might actually be a problem (not giving > the hint when we should), the BEFORE trigger would have to "undo" an > explicit change to an updated column. Uh ... it seems that you are writing as though "giving the hint" means saying that the column value changed. That seems quite confusingly backwards to me, as that is/ought to be the expected assumption. Maybe you should invert the flag state while you are at it. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix memory leak in indexUnchanged hint mechanism.
- db6736c93cb8 15.0 landed
- 41ee68a91f0f 14.2 landed
-
Fix pull_varnos' miscomputation of relids set for a PlaceHolderVar.
- 55dc86eca70b 14.0 cited