| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, "Ben Zeev, Lior" <lior(dot)ben-zeev(at)hp(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Process memory architecture |
| Date: | 2013-05-27 12:26:53 |
| Message-ID: | CA+HiwqH1Zc4ur6ZwNSPknP7wWn9+r2DSLWmMqzpS7h7Tpkvfjw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 27, 2013 at 9:16 PM, Atri Sharma <atri(dot)jiit(at)gmail(dot)com> wrote:
>>> AFAIK, the shared disk buffers are the only part shared between the processes.
>>
>> There's a bit of other information shared, but disk buffers are
>> certainly the bulk of it.
>
> The other information being locks?
CreateSharedMemoryAndSemaphores() (src/backend/storage/ipc/ipci.c)
seems to be the place where we can see what all things reside in
shared memory, since at the beginning of the function, you can see
size being computed for shared memory to hold all the things that need
to be in shared memory.
--
Amit Langote
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2013-05-27 12:27:46 | Re: PostgreSQL Process memory architecture |
| Previous Message | Stephen Frost | 2013-05-27 12:26:48 | Re: Planning incompatibilities for Postgres 10.0 |