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 1pvJE3-00056M-Iv for pgsql-general@arkaria.postgresql.org; Sat, 06 May 2023 14:49:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pvJD3-0003pi-FP for pgsql-general@arkaria.postgresql.org; Sat, 06 May 2023 14:48:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pvJD3-0003pU-5J for pgsql-general@lists.postgresql.org; Sat, 06 May 2023 14:48:29 +0000 Received: from mail-qt1-x82e.google.com ([2607:f8b0:4864:20::82e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pvJCv-000xUh-V8 for pgsql-general@lists.postgresql.org; Sat, 06 May 2023 14:48:28 +0000 Received: by mail-qt1-x82e.google.com with SMTP id d75a77b69052e-3f0b299d739so14575791cf.3 for ; Sat, 06 May 2023 07:48:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683384501; x=1685976501; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=P1l4H5DG1MJqFrURtjOsj8F8qnqNvya7bUW6dPjq6sQ=; b=DpPR9lkrbhiffbhabUL77ooPVH+T6tf49MPBTFZ9HsJ6SJL0EY9l2+23oOQRQhHp7Y tCcqIXom+vZIfAb9g05BR7LL7fVS2Kd+joZZ8cYjHkajuqHDMpNSDDSoLvYk3o6Zebus kORsHRj0RaFybJ0LV/RFpuOedtY7kmnmuNzaAIgQpS1tK1dG0ZH3jKSg7t8Oc8h7lMWz FzbNJl5/8xKxgYFtQJgP2NoLVoDvObtDRm8OI810STLNE6RVtQYHa8Mr4VU0KZTXFah0 iObgA4uI9wmNhyA4qLCHn/a3+zxoC4DfAnpp/HQ5UifiQa4PS63lOEq54UKd+5XgUuBW 7djg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683384501; x=1685976501; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=P1l4H5DG1MJqFrURtjOsj8F8qnqNvya7bUW6dPjq6sQ=; b=YcDB0QX3cOjg+DorkJWKtucdq2YkFaArFQE9/FZ2m9dUhltyKPY89PhOQ0tL5DpGc3 PT66PbnhixBhnoHuU5l8Td+IyaBzBCZlZo//ewp1RWaeEqa0Y4gq1p/oTIzgI/FjtoGD VH+EKjavxahE4v/ZbXdGlOTtwH0rI/uF4z3crtxyqTk2uz2S3xAP9g6RfR+jfFxgHpN6 bMES303228ImaJRXZ6kFRTJrbrHc4YMFGD4mLCD2Uhi7vQulGIwUnkDl/ruNHYuri0kk 3jnKM8FJ45CQ6ijXC1uYopS/8eDfyOen4p6QpcPXGObJCQQ2xHBSQD2ipKLWzb38ncBy YsJA== X-Gm-Message-State: AC+VfDz9oLu3XDMm4u4jEuzh8+NMWksBoyqyT5Gi+Bm9csTby3nFzoUv yJKsBqwe/Bh7QdG8RgxTHLeN5/WExgYkXQ== X-Google-Smtp-Source: ACHHUZ5aLJ40I5OP0dpFaYdlkywrFvqkS12PITcbI2Nn2C2MFjcWOEstOeZfCMRPHC7Pndz5ZcdmIw== X-Received: by 2002:a05:622a:14d4:b0:3ef:5bfc:de92 with SMTP id u20-20020a05622a14d400b003ef5bfcde92mr7864518qtx.55.1683384500372; Sat, 06 May 2023 07:48:20 -0700 (PDT) Received: from ?IPV6:2605:2a00:9005:dead::beef? ([2605:2a00:9005:dead::beef]) by smtp.gmail.com with ESMTPSA id q3-20020a05620a038300b007576ebee9a8sm150897qkm.82.2023.05.06.07.48.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 06 May 2023 07:48:20 -0700 (PDT) Message-ID: Date: Sat, 6 May 2023 10:48:18 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Death postgres Content-Language: en-US To: Marc Millas , "pgsql-general@lists.postgresql.org" References: From: Thomas Guyot In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-05-05 21:14, Marc Millas wrote: > Hi, > > postgres 14.2 on Linux redhat > > temp_file_limit set around 210 GB. > > a select request with 2 left join have crashed the server (oom killer) > after the postgres disk occupation did grow from 15TB to 16 TB. > > What are the cases where postgres may grow without caring about > temp_file_limit ? > > thanks, > Some OSes like IIRC RHEL9 now default to tmpfs for /tmp - if your temp files are written in a tmpfs then it may may very well trigger the OOM because of the temp file used up all RAM. Check the filesystem type of your temp file's location. -- Thomas