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

Re: [ADMIN] shared_buffers and shmmax

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Greg Sabino Mullane <greg(at)turnstep(dot)com>
Cc: pgsql-docs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [ADMIN] shared_buffers and shmmax
Date: 2008-12-15 23:32:36
Message-ID: 200812152332.mBFNWaa26314@momjian.us (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-docspgsql-hackers
I have added this TODO item:

	Rationalize the discrepancy between settings that use values in bytes
	and SHOW that returns the object count
	
        * http://archives.postgresql.org/pgsql-docs/2008-07/msg00007.php 

---------------------------------------------------------------------------

Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> NotDashEscaped: You need GnuPG to verify this message
> 
> 
> >> shared_buffers is in disk block size, typically 8K
> 
> > 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?
> 
> Bite the bullet and start showing the buffer settings as a pure number of bytes
> everywhere, and get rid of the confusing '8kB' unit in pg_settings? Things like
> this don't help our cause:
> 
> test=# show shared_buffers;
>  shared_buffers
> ----------------
>  24MB
> (1 row)
> 
> test=# set temp_buffers = '24MB';
> SET
> 
> test=# show temp_buffers;
>  temp_buffers
> --------------
>  3072
> 
> test=# select name, setting from pg_settings where name ~ 'buffers';
>       name      | setting
> ----------------+---------
>  shared_buffers | 3072
>  temp_buffers   | 3072
>  wal_buffers    | 8
> 
> test=# show wal_buffers;
>  wal_buffers
> -------------
>  64kB
> 
> 
> --
> Greg Sabino Mullane greg(at)turnstep(dot)com
> End Point Corporation
> PGP Key: 0x14964AC8 200807241351
> http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
> -----BEGIN PGP SIGNATURE-----
> 
> iEYEAREDAAYFAkiIwYYACgkQvJuQZxSWSsiY5wCfU/tca+1JakWaMCDDRHEHk/Uj
> 1rcAoMi1FNGSpJhyXWde1psygq6v3MlS
> =gCPg
> -----END PGP SIGNATURE-----
> 
> 
> 
> -- 
> Sent via pgsql-docs mailing list (pgsql-docs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-docs by date

Next:From: Alvaro HerreraDate: 2008-12-15 23:43:37
Subject: Re: [ADMIN] shared_buffers and shmmax
Previous:From: Bruce MomjianDate: 2008-12-15 23:23:02
Subject: Re: [ADMIN] shared_buffers and shmmax

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2008-12-15 23:41:41
Subject: Re: TODO item: Have psql show current values for a sequence
Previous:From: Bruce MomjianDate: 2008-12-15 23:23:02
Subject: Re: [ADMIN] shared_buffers and shmmax

pgsql-admin by date

Next:From: Alvaro HerreraDate: 2008-12-15 23:43:37
Subject: Re: [ADMIN] shared_buffers and shmmax
Previous:From: Bruce MomjianDate: 2008-12-15 23:23:02
Subject: Re: [ADMIN] shared_buffers and shmmax

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