| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Markus Wanner <markus(at)bluegap(dot)ch> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: dynamically allocating chunks from shared memory |
| Date: | 2010-08-09 18:33:08 |
| Message-ID: | 201008091833.o79IX8F11111@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Markus Wanner wrote:
> Hi,
>
> On 08/09/2010 06:10 PM, Bruce Momjian wrote:
> > My point is that you can treat malloc the same as "add shared memory",
> > to some extent, with the same limiations.
>
> Once one of the SLRU buffers is full, it cannot currently allocate from
> another SLRU buffer's unused memory area. That memory there is plain
> wasted at that moment. That's my point and the problem the allocator I
> posted tries to solve.
>
> I fail to see how malloc could help here. malloc() only allocates
> process-local memory.
My point is that we have the same limitations with malloc()/threads, as
we have with shared memory.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-08-09 18:33:54 | Re: dynamically allocating chunks from shared memory |
| Previous Message | Robert Haas | 2010-08-09 18:32:09 | Re: knngist - 0.8 |