From: | Umar Farooq <umarfm13(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Fwd: PostgreSQL Memory Management |
Date: | 2009-03-16 19:43:22 |
Message-ID: | 12e94ce30903161243y2318dd55r85ed1eb81ac909ce@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Hi,
Please find my original message below. This was originally posted to
pgsql-general, but didn't get any response.
Thanks,
-Umar
---------- Forwarded message ----------
From: Umar Farooq <umarfm13(at)gmail(dot)com>
Date: Mon, Mar 9, 2009 at 12:39 PM
Subject: PostgreSQL Memory Management
To: pgsql-general(at)postgresql(dot)org
Hi All,
I have a few general question about PGSQL's internals of memory management
and I think this list is appropriate for that. I am interested to find out:
(1) how does PostgreSQL internally use physical memory allocated to it?
(2) what are different type of allocation units?
(3) what is a particular allocation unit used for e.g., to store log-tail,
query plans, procedure cache etc.?
I've already gone through README file in /backend/src/util/mmgr.
Thanks,
-Umar
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2009-03-16 20:03:01 | Re: Maximum transaction rate |
Previous Message | Scott Marlowe | 2009-03-16 19:13:38 | Re: deployment query |
From | Date | Subject | |
---|---|---|---|
Next Message | Jonah H. Harris | 2009-03-16 20:00:46 | Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client. |
Previous Message | Heikki Linnakangas | 2009-03-16 19:21:29 | Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client. |