Re: PostgreSQL Process memory architecture

From: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
To: "Ben Zeev, Lior" <lior(dot)ben-zeev(at)hp(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL Process memory architecture
Date: 2013-05-27 10:19:24
Message-ID: CAOeZVicpCcgZ33HRrxQv71yQgEfCamZyjgs99G8SQYC8cE7Big@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 27, 2013 at 3:41 PM, Ben Zeev, Lior <lior(dot)ben-zeev(at)hp(dot)com> wrote:
> Hi Atri,
>
> Thanks for your answer!
> Do you have idea what may be the reason that PostgreSQL process consume more memory when there are more partial indexes on the DB table?

Well, I am not too sure, but indexes always take up more space, so if
your backend has a lot of indexes, it will cause the process to
consume more memory.

Indexes should be used with care, as too many indexes can cause a
memory overhead,which can cause performance degradations.

Regards,

Atri

--
Regards,

Atri
l'apprenant

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ben Zeev, Lior 2013-05-27 10:25:17 Re: PostgreSQL Process memory architecture
Previous Message Michael Paquier 2013-05-27 09:45:30 Re: Planning incompatibilities for Postgres 10.0