Re: When Update balloons memory
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Klaudie Willis <Klaudie.Willis@protonmail.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2021-12-15T00:02:23Z
Lists: pgsql-bugs, pgsql-general
On Tue, Dec 14, 2021 at 3:28 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > 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. That's not what I meant. When I say "give the hint", I mean pass "indexUnchanged = true" to aminsert(). This is interpreted within btinsert() as "the incoming index tuple is a duplicate of at least one index, so perform a bottom-up index deletion pass if and when the alternative is splitting the leaf page". In practice the hint always has to be treated as a noisy signal about what might work, as a strategy of last resort, with costs that are imposed on non-HOT updaters. -- Peter Geoghegan
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