From: | Erik Jones <erik(at)myemma(dot)com> |
---|---|
To: | General PostgreSQL List <pgsql-general(at)postgresql(dot)org> |
Subject: | max_*, shared_buffers, and shared memory |
Date: | 2007-10-12 16:51:43 |
Message-ID: | 54B1B7F3-683A-462B-BE75-A4B5378F7DE2@myemma.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hey, everyone, a quick shared memory. So,
max_connections are ~400b per connection
max_prepared_transactions are ~600b per prepared transaction
for lock management the cost is in table slots in units of ~220b per
table slot with total table slots = (max_locks_per_transaction +
(max_connections + max_prepared_transactions))
So, of these settings, which are accounted for as part of
shared_buffers and which result in a system shared memory request on
top of the shared_buffers setting at server start? I ask because I
thought that they were all "on top of" shared_buffers" but the
comment in the config for max_connections mentions raising
shared_buffers to accommodate more.
Erik Jones
Software Developer | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-10-12 16:51:47 | Re: Out of memory with ODBC |
Previous Message | Clemens Schwaighofer | 2007-10-12 16:26:09 | Re: Query problem |