Re: PostgreSQL Process memory architecture

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: "Ben Zeev, Lior" <lior(dot)ben-zeev(at)hp(dot)com>
Cc: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL Process memory architecture
Date: 2013-05-27 11:50:52
Message-ID: CA+HiwqFqR2vm6SRgwgJH4M6yLrDVkh=Xi2z84Jc73K32q0EmTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 27, 2013 at 7:25 PM, Ben Zeev, Lior <lior(dot)ben-zeev(at)hp(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Atri Sharma 2013-05-27 11:55:48 Re: PostgreSQL Process memory architecture
Previous Message Atri Sharma 2013-05-27 11:36:12 Re: PostgreSQL Process memory architecture