On Thu, Jun 29, 2017 at 12:24 PM, Thomas Munro <thomas.mu...@enterprisedb.com> wrote: > fallocate-v5.patch
Added to commitfest so we don't lose track of this. I'm mainly concerned about the fact that we have a way for PostgreSQL to die that looks exactly like a bug, when really it's masking an out-of-memory condition that a DBA or sysadmin would normally be able to diagnose by the appearance of the OOM reaper at the window holding a scythe. I suppose the SIGBUS case is much more likely to happen when we start actively using large amounts of dynamic shared memory (parallel hash), but I suppose it could happen now if your system is already overcommitted and a small DSM segment happens to push you over the edge. -- Thomas Munro http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
