Horton
Menu

Re: When Update balloons memory

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Klaudie Willis <Klaudie.Willis@protonmail.com>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2021-12-07T14:57:53Z
Lists: pgsql-bugs, pgsql-general 
Klaudie Willis <Klaudie.Willis@protonmail.com> writes:
> The following statement below, when not divided up into chunks, but run across all 800M rows, did trigger an OOM-kill from the OS.

An UPDATE should only result in memory bloat if it's queuing trigger
events to be processed at end-of-statement.  You claim there are
no triggers, but are you sure? (what about foreign keys?)

Otherwise, it seems possible that you've identified a memory leak,
but there's not enough detail here to investigate.  Can you create
a reproducible test case?

			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 →

  1. Fix memory leak in indexUnchanged hint mechanism.

  2. Fix pull_varnos' miscomputation of relids set for a PlaceHolderVar.