| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-docs pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Monnerie | 2008-12-17 01:18:55 | Re: slow slow query log |
| Previous Message | Bruce Momjian | 2008-12-16 22:06:53 | Re: [ADMIN] shared_buffers and shmmax |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-12-17 01:33:36 | Re: [ADMIN] shared_buffers and shmmax |
| Previous Message | Bruce Momjian | 2008-12-16 22:06:53 | Re: [ADMIN] shared_buffers and shmmax |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-12-16 23:45:35 | Re: Another issue in default-values patch: defaults expanded too soon |
| Previous Message | Tom Lane | 2008-12-16 23:28:07 | Re: Another issue in default-values patch: defaults expanded too soon |