Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p6zKy-0003Jy-Ts for pgsql-performance@arkaria.postgresql.org; Sun, 18 Dec 2022 19:28:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p6zKw-0005yK-6z for pgsql-performance@arkaria.postgresql.org; Sun, 18 Dec 2022 19:28:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p6zKv-0005xa-TQ for pgsql-performance@lists.postgresql.org; Sun, 18 Dec 2022 19:28:37 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p6zKs-0005yx-UB for pgsql-performance@lists.postgresql.org; Sun, 18 Dec 2022 19:28:36 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 2BIJSWss462806; Sun, 18 Dec 2022 14:28:33 -0500 From: Tom Lane To: Frits Jalvingh cc: pgsql-performance@lists.postgresql.org Subject: Re: Fwd: temp_file_limit? In-reply-to: References: <20221218155705.GT1153@telsasoft.com> Comments: In-reply-to Frits Jalvingh message dated "Sun, 18 Dec 2022 18:29:41 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <462804.1671391712.1@sss.pgh.pa.us> Date: Sun, 18 Dec 2022 14:28:32 -0500 Message-ID: <462805.1671391712@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Frits Jalvingh writes: > Just to be clear: my real question is: why is temp_file_limit not working > at the specified size? I've not looked at that code lately, but I strongly suspect that it's implemented in such a way that it's a per-process limit, not a per-session limit. So each parallel worker could use up that much space. It's also possible that you've found an actual bug, but without a reproducer case nobody's going to take that possibility too seriously. We're unlikely to accept "the limit should work across multiple processes" as a valid bug though. That would require a vastly more complicated implementation. regards, tom lane