| From: | Anton Maksimenkov <anton200(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Subject: | Re: Memory Usage and OpenBSD |
| Date: | 2010-02-10 10:13:58 |
| Message-ID: | 8cac8dd1002100213y4668690em421047a20c3c9f76@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2010/2/10 Martijn van Oosterhout <kleptog(at)svana(dot)org>:
>> Can anybody briefly explain me how one postgres process allocate
>> memory for it needs?
>
> There's no real maximum, as it depends on the exact usage. However, in
> general postgres tries to keep below the values in work_mem and
> maintainence_workmem. Most of the allocations are quite small, but
> postgresql has an internal allocator which means that the system only
> sees relatively large allocations.
These "relatively large allocations" are exactly what I mean. What
size are they?
Is it right to say that these allocations are work_mem size, or
temp_buffers size, or maintainence_workmem size? Or something like.
--
antonvm
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AI Rumman | 2010-02-10 10:23:27 | Re: when a table was last vacuumed |
| Previous Message | Guillaume Lelarge | 2010-02-10 10:12:48 | Re: when a table was last vacuumed |