From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: valiouk@yahoo.co.uk, pgsql-docs@postgresql.org, dx k9 <bitsandbytes88@hotmail.com>
Subject: Re: [ADMIN] shared_buffers and shmmax
Date: Wed, 17 Dec 2008 08:53:44 -0500
Message-ID: <27841.1229522024@sss.pgh.pa.us> (raw)
In-Reply-To: <200812171341.mBHDfeK11281@momjian.us>
References: <200812171341.mBHDfeK11281@momjian.us>
Bruce Momjian <bruce@momjian.us> writes:
> Tom Lane wrote:
>> * If we do it like this then the left-hand column is really redundant,
>> not to say wrong because the right-hand formulas depend on more than
>> the single variable mentioned. How about something like
>>
>> Table 17-2 PostgreSQL shared memory usage
>>
>> Purpose Approximate number of bytes required (as of 8.3)
>>
>> Per-connection state (1800 + 270 * max_locks_per_transaction) * max_connections
>> Autovacuum worker state (1800 + 270 * max_locks_per_transaction) * autovacuum_max_workers
>> Prepared transaction state ...
>> Shared disk buffers ...
>> WAL buffers ...
>> Fixed space requirements 770kB
> OK, I updated it again:
> http://momjian.us/tmp/pgsql/kernel-resources.html> I did change your left column wording because it could be interpreted as
> something that changes during server execution, e.g. connections.
[ shrug... ] I don't find what you did to be an improvement over what
I suggested, but I don't have time to argue about it.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, alvherre@commandprompt.com, bitsandbytes88@hotmail.com
Subject: Re: [ADMIN] shared_buffers and shmmax
In-Reply-To: <27841.1229522024@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox