Klaudie Willis <Klaudie.Willis@xxxxxxxxxxxxxx> 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
