Skip site navigation (1) Skip section navigation (2)

Re: [ADMIN] shared_buffers and shmmax

From: "Francisco Reyes" <lists(at)stringsutils(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-docs(at)postgreSQL(dot)org>, <bitsandbytes88(at)hotmail(dot)com>, <valiouk(at)yahoo(dot)co(dot)uk>
Subject: Re: [ADMIN] shared_buffers and shmmax
Date: 2008-07-22 19:30:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-adminpgsql-docspgsql-hackers
On 10:45 am 07/22/08 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> [ redirecting to pgsql-docs ]
> number-of-buffers.  I agree it's not entirely obvious that what it
> means is "multiply your setting in KB/MB by 8400/8192".  Anybody have
> an idea how to clarify things?

Perhaps changing the table title?
Table 17-2. Configuration parameters affecting PostgreSQL's shared memory
usage when not using a size modified.

Alternatively, below the table we could have clarifications such as:
Previously, it was not possible to indicate a size modified such as M for
Megabytes. As of version X.Y, Postgresql allows to use M, for MB, GB for GB
and more... See.... for all values.

When not using one of the new modifiers the space used would be the number
you enter times the constant on the right side of the table.
For example using 100 shared_buffers would be 100 x 8400  = 840,000 bytes.

In response to

pgsql-docs by date

Next:From: Greg Sabino MullaneDate: 2008-07-24 17:54:31
Subject: Re: [ADMIN] shared_buffers and shmmax
Previous:From: Tom LaneDate: 2008-07-22 14:45:59
Subject: Re: [ADMIN] shared_buffers and shmmax

pgsql-hackers by date

Next:From: Simon RiggsDate: 2008-07-22 19:51:45
Subject: Re: Do we really want to migrate plproxy and citext intoPG core distribution?
Previous:From: Tom LaneDate: 2008-07-22 19:01:04
Subject: Re: [PATCHES] GIN improvements

pgsql-admin by date

Next:From: Gibson ChimhamhiwaDate: 2008-07-23 09:23:41
Subject: Re: Welcome to the pgsql-admin list!
Previous:From: Shane AmblerDate: 2008-07-22 18:47:51
Subject: Re: conditional logging based on client

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group