AW: Out of memory in big transactions after upgrade to 12.2

Thanks a lot so far for all your answers. work_mem is 4 MB and max_connections is 100, no pooling.

As additional info maybe I should mention that we do an update on one table which cascades to some other tables updating 10ks of rows there and triggering the Perl functions for every row. I’m not sure this was clear from the stack trace.

Von: Michael Lewis [mailto:mlewis(at)entrata(dot)com]
Gesendet: Freitag, 3. April 2020 18:30
An: David Day <djd2403(at)gmail(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>; Jan Strube <Jan(dot)Strube(at)solvians(dot)com>; pgsql-general(at)lists(dot)postgresql(dot)org
Betreff: Re: Out of memory in big transactions after upgrade to 12.2

If you didn't turn it off, you have parallel workers on by default with v12. If work_mem is set high, memory use may be much higher as each node in a complex plan could end up executing in parallel.

Also, do you use a connection pooler such as pgbouncer or pgpool? What is max_connections set to?