Re: PostgreSQL Process memory architecture - Mailing list pgsql-hackers

From Amit Langote
Subject Re: PostgreSQL Process memory architecture
Date
Msg-id CA+HiwqFqR2vm6SRgwgJH4M6yLrDVkh=Xi2z84Jc73K32q0EmTQ@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL Process memory architecture  ("Ben Zeev, Lior" <lior.ben-zeev@hp.com>)
Responses Re: PostgreSQL Process memory architecture  (Atri Sharma <atri.jiit@gmail.com>)
List pgsql-hackers
On Mon, May 27, 2013 at 7:25 PM, Ben Zeev, Lior <lior.ben-zeev@hp.com> wrote:
> Thanks Atri!
>
> Do you know why PostgreSQL store the indexes in memory per process and not in the shared memory?
> Is there a way to prevent it store the indexes data per process, and force it storing it in the shared memory?
>

An index is built in backend process's local memory, but, when
accessing, index pages are stored in shared memory. That is, for
example, when an index scan is performed, index pages are brought into
shared memory and accessed from there.


--
Amit Langote



pgsql-hackers by date:

Previous
From: Atri Sharma
Date:
Subject: Re: PostgreSQL Process memory architecture
Next
From: Atri Sharma
Date:
Subject: Re: PostgreSQL Process memory architecture