| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, "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-18 04:30:07 |
| Message-ID: | 28340.1403065807@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
> On Wed, Jun 18, 2014 at 2:09 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> On the other hand, this approach would entirely fail to account for
>> non-palloc'd allocations, which could be a significant issue in some
>> contexts.
> Won't it be possible if we convert malloc calls in backend code to
> go through wrapper, we already have some precedents of same like
> guc_malloc, pg_malloc?
We do not have control over mallocs done by third-party code
(think pl/perl for example). mallocs done by our own code are
fairly insignificant, I would hope.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mitsumasa KONDO | 2014-06-18 05:44:25 | Re: gaussian distribution pgbench |
| Previous Message | Abhijit Menon-Sen | 2014-06-18 04:07:54 | Re: postgresql.auto.conf read from wrong directory |