Re: Shared memory estimation for postgres

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: leoaaryan <leoaaryan(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Shared memory estimation for postgres
Date: 2016-11-11 00:56:21
Message-ID: CAB7nPqSY4PTregu42HN24zFpLhiXFqewbNHPFPu+6aEy=nKd9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 11, 2016 at 8:40 AM, leoaaryan <leoaaryan(at)gmail(dot)com> wrote:
> The easiest way to find the value for the shared memory computation is to
> change the logging level to DEBUG3 and start postgres DB engine and it will
> give the calculated value in the log file.
>
> I believe postgres as a DB needs to be running for any extension to run (I
> may be wrong here) and I dont want to start the database for this analysis.
>
> Please correct me if I'm wrong in my concepts or if I've not understood
> anything.

Some time ago a patch has been proposed to project to a system view
the shared memory allocations currently happening on an instance:
https://www.postgresql.org/message-id/20140504114417.GM12715@awork2.anarazel.de
This could be plugged into its own extension rather easily. Note
though that DSM segments (dynamic shared memory) do not have names
associated to them which would be helpful if you'd like to track that
as well. But perhaps you don't care much.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2016-11-11 02:04:21 Re: Floating point comparison inconsistencies of the geometric types
Previous Message Tsunakawa, Takayuki 2016-11-11 00:54:20 Re: Remove the comment on the countereffectiveness of large shared_buffers on Windows