| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Klaudie Willis <Klaudie(dot)Willis(at)protonmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: When Update balloons memory |
| Date: | 2021-12-07 14:57:53 |
| Message-ID: | 3484560.1638889073@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
Klaudie Willis <Klaudie(dot)Willis(at)protonmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bossart, Nathan | 2021-12-07 22:04:54 | Re: BUG #17268: Possible corruption in toast index after reindex index concurrently |
| Previous Message | Ian R. Campbell | 2021-12-07 14:08:49 | Re: range_agg() missing support for multirange inputs |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zwettler Markus (OIZ) | 2021-12-07 16:10:25 | error connecting to pgbouncer admin console |
| Previous Message | Tom Lane | 2021-12-07 14:45:38 | Re: how to get value of parameter set in session for other user |