Re: Postgresql OOM - Mailing list pgsql-hackers

From Radu Radutiu
Subject Re: Postgresql OOM
Date
Msg-id CAG4TxrgQ5V00eYTaRhPUbfp8Gnhzr4i2YooMGOhXW8U6RMmzNA@mail.gmail.com
Whole thread Raw
In response to Re: Postgresql OOM  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers

FWIW, it can be useful to configure the OS with strict memory overcommit. That
causes postgres to fail more gracefully, because the OOM killer won't be
invoked.

In the current setup the database is used as an embedded db, with the application sharing the same host as the database. Setting the memory overcommit affects the other application, but configuring LimitAS for the postgresql systemd service should work. 
Does this mean that the fact that this query uses more than 100x the configured work_mem is not considered a bug? Should I create a bug report?
 

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Non-text mode for pg_dumpall
Next
From: Robert Haas
Date:
Subject: Re: Reuse child_relids in try_partitionwise_join was Re: Assert failure on bms_equal(child_joinrel->relids, child_joinrelids)