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 1frrFV-0007mh-9L for pgsql-admin@arkaria.postgresql.org; Mon, 20 Aug 2018 20:58:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1frrFT-0003Uj-HE for pgsql-admin@arkaria.postgresql.org; Mon, 20 Aug 2018 20:58:03 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1frrFT-0003Uc-6g for pgsql-admin@lists.postgresql.org; Mon, 20 Aug 2018 20:58:03 +0000 Received: from resqmta-ch2-09v.sys.comcast.net ([2001:558:fe21:29:69:252:207:41]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1frrFQ-0004YC-6o for pgsql-admin@postgresql.org; Mon, 20 Aug 2018 20:58:01 +0000 Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id ricofie4G5zkYrrFMfLJo8; Mon, 20 Aug 2018 20:57:56 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1534798676; bh=AISSge8iP2WwNw/wrJOn5UybAPDkOL4/9eiLpC+zf6c=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=eia9gPKUEeKrE8zwiGE8pVtiDDF+VHH5hyJqx6ocxaBe0WSU06Du3WzrA23bACBdc ZlExqc/MjfDUAHLkYYHjpA7h2Dgha1/goY0MpP1ACgsLvyh6+zmyqcgL5CbBPykfim 9/hN3eoRS9lc9XLqwEdeSIl+X2nFMABGBm1dEL8aZI7mUoXj9lmO7ScF2cUrhlsAso BqAbidtjXHZVJS9FLnVYqqAfXgeWCY8l6tj5GetsrbaagE7dxNhFzDUCeKxyLDwSIA eCczc9mSZmDXoBhTddwc5ApamrnljrM0q6+RJ4Ks0EqA4GzvSUxx9nPUyLqHuvvKmI NLTwkdCU3VInw== Received: from jsievers.comcast.net ([12.30.159.20]) by resomta-ch2-12v.sys.comcast.net with ESMTPA id rrF7fMJP8vhw1rrF7fMkT9; Mon, 20 Aug 2018 20:57:54 +0000 Received: from jsievers.enova.com (localhost [127.0.0.1]) by jsievers.comcast.net (Postfix) with ESMTP id 4F8F7260056; Mon, 20 Aug 2018 15:57:41 -0500 (CDT) From: Jerry Sievers To: Jerry Sievers Cc: Erwin Fritz , 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> <87k1okg44t.fsf@jsievers.enova.com> Date: Mon, 20 Aug 2018 15:57:41 -0500 In-Reply-To: <87k1okg44t.fsf@jsievers.enova.com> (Jerry Sievers's message of "Mon, 20 Aug 2018 15:44:02 -0500") Message-ID: <87ftz8g3i2.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: MS4wfLmV+JTYDO1BRKijVTP6XuPK+cXOUK8zId5yIMFULJveN6YwsMqUHE8piUd9x0b81Aba3FAM7flqPyaOV4ot/cub84EePmvvqEb5Bu5EKVAGzQduxD2U UXt3ULNgGg4tLF2QoeBuNso+NmhPTAcd5yfXK4jMMqrdeFmaWNG3kQ1i3H48abvhmq40G8PdjdBkJJG7K4mh+411hvEmb4kvb4tzjdBUK8avx87LxmBmOisF DQ9mcErnAxUiq7XvYrM8n7W+ziRC05Jp4WyG32NdCaKW7Ozlc8RjdyQ3L3uGbaajjRRey1QTJZMuKwTLCO3qzA== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Jerry Sievers writes: > 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; oops! Pardon me. only superuser can frob that setting so this advice I gave immediately above might not help you. > > 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