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

Re: [ADMIN] shared_buffers and shmmax

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, valiouk(at)yahoo(dot)co(dot)uk, pgsql-docs(at)postgresql(dot)org, dx k9 <bitsandbytes88(at)hotmail(dot)com>
Subject: Re: [ADMIN] shared_buffers and shmmax
Date: 2008-12-16 23:38:17
Message-ID: 17528.1229470697@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-docspgsql-hackers
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> OK, updated patch.  I added item descriptions and removed Alvaro's
> paragraph;  I worked with Alvaro on this patch.

This still seems pretty misleading, as for example
  
>        <tbody>
>         <row>
>          <entry><xref linkend="guc-max-connections"></>
> !        <entry>1800 + 270 * <xref
> !        linkend="guc-max-locks-per-transaction"> bytes per connection</entry>
>         </row>

sounds like it might mean bytes per *active* connection, when of course
the correct way to figure it is by multiplying by max_connections.
If you're going to give a formula, why not just give a formula, eg

	(1800 + 270 * max_locks_per_transaction) * (max_connections + autovacuum_max_workers)

			regards, tom lane

In response to

Responses

pgsql-docs by date

Next:From: Bruce MomjianDate: 2008-12-17 01:33:36
Subject: Re: [ADMIN] shared_buffers and shmmax
Previous:From: Bruce MomjianDate: 2008-12-16 22:06:53
Subject: Re: [ADMIN] shared_buffers and shmmax

pgsql-hackers by date

Next:From: Gregory StarkDate: 2008-12-16 23:45:35
Subject: Re: Another issue in default-values patch: defaults expanded too soon
Previous:From: Tom LaneDate: 2008-12-16 23:28:07
Subject: Re: Another issue in default-values patch: defaults expanded too soon

pgsql-admin by date

Next:From: Michael MonnerieDate: 2008-12-17 01:18:55
Subject: Re: slow slow query log
Previous:From: Bruce MomjianDate: 2008-12-16 22:06:53
Subject: Re: [ADMIN] shared_buffers and shmmax

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