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 1frr2L-00071l-I7 for pgsql-admin@arkaria.postgresql.org; Mon, 20 Aug 2018 20:44:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1frr2J-0005UQ-8P for pgsql-admin@arkaria.postgresql.org; Mon, 20 Aug 2018 20:44:27 +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 1frr2I-0005UJ-Ip for pgsql-admin@lists.postgresql.org; Mon, 20 Aug 2018 20:44:27 +0000 Received: from resqmta-ch2-04v.sys.comcast.net ([2001:558:fe21:29:69:252:207:36]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1frr2E-0006GT-Gv for pgsql-admin@postgresql.org; Mon, 20 Aug 2018 20:44:25 +0000 Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-04v.sys.comcast.net with ESMTP id rn6EfBnum5YMfrr27f82Yy; Mon, 20 Aug 2018 20:44:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1534797855; bh=qGno0Xy/srh106rd6fJm7LN2QFpch2S7V8qobqwodMA=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=cjCa+xcj/xsSzaZebY6XHPk4CLh9yPLoSSC3XxMWyH67a4pmFwzuqVKMnqmQgz8ZD U33GylCSmalgSl8TeiX7x/JXInAdvDP6YoTGChSTxQLt7F1nfRrAOiuTIckGD2AI+G KUtNHC6DxU6L/JPDo1X23ugNRVxok2R8pLbxZ7g1pc0EIRIlvcOmg2ZZwLysQUyLWn HVH1u/43rXBiQ9k4qvrCPLgnzyYNBxOyBG1Jfu5HdS34fH8eKAhF0hDOgZBH2wX4No sfuLW8BYR/3HNEk5VvfUSLAqP/I6f6Q8DcVW7eTXlI2aubFG/JGNqE0Ypy+wcxrAwW F6sUi311PqibA== Received: from jsievers.comcast.net ([12.30.159.20]) by resomta-ch2-02v.sys.comcast.net with ESMTPA id rr1ufhnMhLaUdrr1vfcKRw; Mon, 20 Aug 2018 20:44:13 +0000 Received: from jsievers.enova.com (localhost [127.0.0.1]) by jsievers.comcast.net (Postfix) with ESMTP id BA3DE260056; Mon, 20 Aug 2018 15:44:02 -0500 (CDT) From: Jerry Sievers To: Erwin Fritz Cc: Tom Lane , Johannes Truschnigg , "pgsql-admin\@postgresql.org" Subject: Re: temp_file_limit parameter ignored? References: <9E6E27BCA0E8EE478089F158D73AF936A91EB443@Exch10-Mailbox.corp.gljpc.com> <20180820131535.ljrnxgph62ypus2z@vault.lan> <9E6E27BCA0E8EE478089F158D73AF936A91ED957@Exch10-Mailbox.corp.gljpc.com> <19727.1534778771@sss.pgh.pa.us> <9E6E27BCA0E8EE478089F158D73AF936A91F367A@Exch10-Mailbox.corp.gljpc.com> Date: Mon, 20 Aug 2018 15:44:02 -0500 In-Reply-To: <9E6E27BCA0E8EE478089F158D73AF936A91F367A@Exch10-Mailbox.corp.gljpc.com> (Erwin Fritz's message of "Mon, 20 Aug 2018 20:09:03 +0000") Message-ID: <87k1okg44t.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 X-CMAE-Envelope: MS4wfHYaKmaamoWTvuneqkzcj4cH2Wk/Z6oAMT61juYpQSd9WvWx2RmhAEkmTY2OUJ5ih7mwh7Owux8sJoHewMQtvrgN9PYgQ4tI6ajhmFY8OQ/i8QJZWyhi gB5+Fh5E18BfLM6OglHFkGGo+FFOuPGiGy0B2nm0DbKweyttG+lz+bydKms5A6+b2eO30wm0iFwuW5Ba8bktV83FLw+1IGsGeLZbP4a+ioX710gppWIdhBcv FCI19lyXiaOEaZH2CCSYqJp1I34azfSNAHMX9NB8BVh5Zd57wsN/yELApO09xiEI List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Erwin Fritz writes: > Here's the output: > > select * from pg_settings where name = 'temp_file_limit'; > -[ RECORD 1 ]---+------------------------------------------------------------------- > name | temp_file_limit > setting | 4194304 > unit | kB > category | Resource Usage / Disk > short_desc | Limits the total size of all temporary files used by each session. > extra_desc | -1 means no limit. > context | superuser > vartype | integer > source | database ^^^^^ This means someone/thing said... ALTER DATABASE $foodb SET temp_file_limit to '$whatever'; See psql \drds. Just do an explicit override in your own job prior to the code that errors out due to resource shortfall. SET temp_file_limit to -1; HTH > min_val | -1 > max_val | 2147483647 > enumvals | > boot_val | -1 > reset_val | 4194304 > sourcefile | > sourceline | > pending_restart | f > > > > > ----------------------------- > This message is intended only for the recipient(s) to which it is > addressed and may contain information that is privileged and > confidential. If you have received this message in error, please > notify the sender immediately and delete all copies. > ----------------------------- > > ________________________________________ > From: Tom Lane [tgl@sss.pgh.pa.us] > Sent: August 20, 2018 09:26 > To: Erwin Fritz > Cc: Johannes Truschnigg; pgsql-admin@postgresql.org > Subject: Re: temp_file_limit parameter ignored? > > Erwin Fritz writes: >> Hmm. I did that, and the sourcefile and sourceline values are blank. I then ran "show config_file" and the result has the correct location of the file. > > What does the "source" column say? > > regards, tom lane > > -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800