From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unchecked malloc |
Date: | 2005-09-27 05:40:07 |
Message-ID: | 8059.1127799607@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> writes:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote
>> No, because you're thinking in terms of the backend environment, and
>> generally in the backend the answer to "when to use malloc directly"
>> is "never".
> Well, except before MemoryContext mechanism is set up? For example, the
> functions(e.g., GUC, vfd) used during bootstrap.
I think you need to take another look at the startup sequences. Those
modules are not run before MemoryContextInit. In any case, the odds
of running out of memory before we get to MemoryContextInit are so small
that I don't have a problem with crashing if it happens.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paesold | 2005-09-27 06:07:04 | Re: State of support for back PG branches |
Previous Message | Ron Peacetree | 2005-09-27 05:09:19 | Re: [PERFORM] A Better External Sort? |