From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | valiouk(at)yahoo(dot)co(dot)uk |
Cc: | pgsql-docs(at)postgreSQL(dot)org, dx k9 <bitsandbytes88(at)hotmail(dot)com> |
Subject: | Re: [ADMIN] shared_buffers and shmmax |
Date: | 2008-07-22 14:45:59 |
Message-ID: | 28167.1216737959@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-docs pgsql-hackers |
[ redirecting to pgsql-docs ]
Valentin Bogdanov <valiouk(at)yahoo(dot)co(dot)uk> writes:
>> From: dx k9 <bitsandbytes88(at)hotmail(dot)com>
>> I'm trying to understand what the documentation means
>> by bytes per increment, what is the increment supposed to
>> be bytes, MB, or Kb.
> shared_buffers is in disk block size, typically 8K, at least that's what it is on Linux platforms. shmmax is quite simply in bytes.
The table the OP is looking at (table 17.2 in the 8.3 docs) predates
the ability to specify shared_buffers in KB or MB instead of
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?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar Mallah | 2008-07-22 17:40:11 | Re: conditional logging based on client |
Previous Message | Valentin Bogdanov | 2008-07-22 14:08:32 | Re: shared_buffers and shmmax |
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Reyes | 2008-07-22 19:30:21 | Re: [ADMIN] shared_buffers and shmmax |
Previous Message | Valentin Bogdanov | 2008-07-22 14:08:32 | Re: shared_buffers and shmmax |
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2008-07-22 14:50:05 | Re: [patch] plproxy v2 |
Previous Message | Zdenek Kotala | 2008-07-22 14:42:18 | Re: pltcl_*mod commands are broken on Solaris 10 |