Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1goYJ3-0005Nf-C3 for pgsql-performance@arkaria.postgresql.org; Tue, 29 Jan 2019 18:40:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1goYJ2-0001t5-3r for pgsql-performance@arkaria.postgresql.org; Tue, 29 Jan 2019 18:40:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1goYJ1-0001sx-Sm for pgsql-performance@lists.postgresql.org; Tue, 29 Jan 2019 18:40:19 +0000 Received: from resqmta-ch2-03v.sys.comcast.net ([2001:558:fe21:29:69:252:207:35]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1goYIz-0003Rt-Ck for pgsql-performance@lists.postgresql.org; Tue, 29 Jan 2019 18:40:19 +0000 Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-03v.sys.comcast.net with ESMTP id oToSgJaAv2FoJoYIvgnT33; Tue, 29 Jan 2019 18:40:13 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1548787213; bh=iub8HrxTz9NLfW33rqmDeB63BOoLmj8ofJeNbdQDfKU=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=OLrwYj33CC/rwfU5ZZEtWAgoSfb2t4S+/FlVSUDZsbcI5KudrjoGN/dCh5RgDhRWL YoXgHRRI73t+MQNlNfppRCERo3B/x2NZ7K3yNYAqkB/kv1nGKA9KSe+IvcK/AxUAIQ uUEXJ0Vi/aZtcw12BlKtw6w5moXEy+lVVuwTLI8m81RRhPHs6+lbkfKn+VABwAJIOf ZJWDwMFykSVqU70pIl9veLutZwPTGzG/79ERSc42BRCxZqu4gzCLKrhrKO+SVqr/3t P2MBuigHF1hkm/qRWuugpz7j4F65rvssTSzQ80I9+B+XlYoDFSWCR6C1dYb3gXO4Sa l2ovgV28VrYTg== Received: from jsievers.comcast.net ([12.187.116.132]) by resomta-ch2-05v.sys.comcast.net with ESMTPA id oYIjggCJEl0TEoYIjg4Mzp; Tue, 29 Jan 2019 18:40:09 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedtledrjedvgdduudejucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnegoteeftdduqddtudculdduhedmnecujfgurhephffvufhfffgjkfgfgggtsehttdertddtredtnecuhfhrohhmpeflvghrrhihucfuihgvvhgvrhhsuceoghhsihgvvhgvrhhsudelsegtohhmtggrshhtrdhnvghtqeenucfkphepuddvrddukeejrdduudeirddufedvnecurfgrrhgrmhephhgvlhhopehjshhivghvvghrshdrtghomhgtrghsthdrnhgvthdpihhnvghtpeduvddrudekjedrudduiedrudefvddpmhgrihhlfhhrohhmpehgshhivghvvghrshduleestghomhgtrghsthdrnhgvthdprhgtphhtthhopehgshhivghvvghrshduleestghomhgtrghsthdrnhgvthdprhgtphhtthhopegsohgsjhholhhlihhffhgvsehgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqphgvrhhfohhrmhgrnhgtvgeslhhishhtshdrphhoshhtghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptd X-Xfinity-VMeta: sc=-85;st=legit Received: from jsievers.enova.com (localhost [127.0.0.1]) by jsievers.comcast.net (Postfix) with ESMTP id 2EF32260056; Tue, 29 Jan 2019 12:40:01 -0600 (CST) From: Jerry Sievers To: Jerry Sievers Cc: Bob Jolliffe , pgsql-performance@lists.postgresql.org Subject: Re: Interpreting shared_buffers setting References: <87k1in9uy0.fsf@jsievers.enova.com> Date: Tue, 29 Jan 2019 12:40:01 -0600 In-Reply-To: <87k1in9uy0.fsf@jsievers.enova.com> (Jerry Sievers's message of "Tue, 29 Jan 2019 12:31:51 -0600") Message-ID: <87fttb9uke.fsf@jsievers.enova.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Jerry Sievers writes: > Bob Jolliffe writes: > >> Excuse me if this is a silly question. I am trying to fiddle with >> shared_buffers setting on postgresql 10.6 on ubuntu 18.04 server. >> >> I have this at bottom of my config file: >> shared_buffers = 1GB >> >> Yet when I check the setting from pg_setting I see something quite different: >> >> postgres=# SELECT name, setting FROM pg_settings where name = 'shared_buffers'; >> name | setting >> ----------------+--------- >> shared_buffers | 131072 Aaaaay! Pasted junk... Here's what I meant. meta_a:postgres# select setting from pg_settings where name='shared_buffers'; setting --------- 131072 (1 row) meta_a:postgres# show shared_buffers; shared_buffers ---------------- 1GB (1 row) > > Why not use the show command which is good about output in human > terms... > > psql (11.1 (Ubuntu 11.1-1.pgdg16.04+1)) > Type "help" for help. > > meta_a:postgres# select name, setting from pg_settings where name = 'shared_buffers'); > ERROR: syntax error at or near ")" > LINE 1: ...me, setting from pg_settings where name = 'shared_buffers'); > ^ > meta_a:postgres# > >> >> Is this a question of units? It looks like 128M. Note when I change >> the setting to 2GB in conf file I see 262144 from pg_setting. I am >> now unsure what the actual shared_buffers allocation is. I cant see >> anything in the docs which tells me how to interpret the integer. >> >> Any clarification welcome. >> >> Regards >> Bob >> >> -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net