Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gCZ5E-00050P-FM for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Oct 2018 23:49:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gCZ59-0000zZ-RM for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Oct 2018 23:48:59 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1gCZ59-0000yl-JE for pgsql-hackers@lists.postgresql.org; Tue, 16 Oct 2018 23:48:59 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gCZ50-0006iw-11 for pgsql-hackers@postgresql.org; Tue, 16 Oct 2018 23:48:56 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w9GNmgnj013250; Tue, 16 Oct 2018 19:48:42 -0400 From: Tom Lane To: Andres Freund cc: Robert Haas , "pgsql-hackers@postgresql.org" , Thomas Munro Subject: Re: Large writable variables In-reply-to: <20181016193303.hqpduztwt6ufmasm@alap3.anarazel.de> References: <20181015200754.7y7zfuzsoux2c4ya@alap3.anarazel.de> <20181016193303.hqpduztwt6ufmasm@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Tue, 16 Oct 2018 12:33:03 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13248.1539733722.1@sss.pgh.pa.us> Date: Tue, 16 Oct 2018 19:48:42 -0400 Message-ID: <13249.1539733722@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk BTW, I looked around for .o files with large BSS numbers, and came across $ size src/interfaces/ecpg/ecpglib/prepare.o text data bss dec hex filename 4023 4 1048576 1052603 100fbb src/interfaces/ecpg/ecpglib/prepare.o That megabyte is from a statically allocated statement cache array. Seems a bit unfriendly to users of ecpglib, given that many apps would never use the statement cache (AFAICT you have to explicitly ask for auto-prepare mode to get to that code). Doesn't look hard to fix though. regards, tom lane