From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>
Subject: Re: Large writable variables
Date: Tue, 16 Oct 2018 19:48:42 -0400
Message-ID: <13249.1539733722@sss.pgh.pa.us> (raw)
In-Reply-To: <20181016193303.hqpduztwt6ufmasm@alap3.anarazel.de>
References: <20181015200754.7y7zfuzsoux2c4ya@alap3.anarazel.de>
<CA+Tgmobk-6=b2KLRRMUWGNWi9KzKrx=WNszr7DDE+QCuwNyrEQ@mail.gmail.com>
<20181016193303.hqpduztwt6ufmasm@alap3.anarazel.de>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, robertmhaas@gmail.com, thomas.munro@enterprisedb.com
Subject: Re: Large writable variables
In-Reply-To: <13249.1539733722@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox