Re: Built-in support for a memory consumption ulimit?

From: Greg Stark <stark(at)mit(dot)edu>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Built-in support for a memory consumption ulimit?
Date: 2014-06-16 20:34:38
Message-ID: CAM-w4HMOrP9B1Ncp6E5pnibA17u=_+YQMNONA1mmPZNBZinwow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 16, 2014 at 9:08 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> What happens if the limit is exceeded? ERROR? FATAL? PANIC?

Well presumably it just makes malloc return NULL which causes an
ERROR. One advantage to setting it via a GUC is that it might be
possible to, for example, raise it automatically in critical sections
or during error unwinding.

--
greg

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-06-16 20:36:36 Re: Built-in support for a memory consumption ulimit?
Previous Message Alvaro Herrera 2014-06-16 20:30:45 Re: Autonomous Transaction (WIP)