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>
Subject: Re: When Update balloons memory
Date: Tue, 07 Dec 2021 09:57:53 -0500
Message-ID: <3484560.1638889073@sss.pgh.pa.us> (raw)
In-Reply-To: <wJYzIcLjhFnsbCK8sy4lZZAojx7m04FwjsGF4WbrKj0gj2wLpaycQSEN1mtBUlhSAQGRvEdxZTwWRNV39UevSNWg8-h-tvWAL61pV4IuhW4=@protonmail.com>
References: <wJYzIcLjhFnsbCK8sy4lZZAojx7m04FwjsGF4WbrKj0gj2wLpaycQSEN1mtBUlhSAQGRvEdxZTwWRNV39UevSNWg8-h-tvWAL61pV4IuhW4=@protonmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, Klaudie.Willis@protonmail.com, pgsql-general@lists.postgresql.org
Subject: Re: When Update balloons memory
In-Reply-To: <3484560.1638889073@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox