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 1pv9N7-0008WD-Ft for pgsql-general@arkaria.postgresql.org; Sat, 06 May 2023 04:18:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pv9N5-0001GC-KB for pgsql-general@arkaria.postgresql.org; Sat, 06 May 2023 04:18:11 +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 1pv9N4-0001DX-HF for pgsql-general@lists.postgresql.org; Sat, 06 May 2023 04:18:11 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pv9Mw-000nIU-SR for pgsql-general@lists.postgresql.org; Sat, 06 May 2023 04:18:09 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 9FA063200976; Sat, 6 May 2023 00:18:00 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sat, 06 May 2023 00:18:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1683346680; x=1683433080; bh=cgbOS+7invuWPF/9WinZCthXBd3LjpGpyKa Lrw20mN4=; b=dEtK4x0pfwWhgH3FrhBBFzjce1WzDRtj906uLXXHsXuLYoAwkAi ST233QTeRV9s3iQoyn+B7kCLeXZZziNgy8KDKztdase7+adZsq07kRQ3ueXS0999 bMDIoWyK2Xqy90S3/GY/TIECueYNWof8acz6DfbV6cjE7RvDZYpxDG2Cz+gobgq7 ZspKV8XAchsIs03xC6OYHCjchwT07LM8TVy9usbzeKLRQCVPnD9aL8v6Nnmq1fU/ NlHHSAiZUQV/GVgdLrVUasTiZW8HBrV4x6shkwcG1m3b1s5sQjmTJrIgON3mKE67 2IQGPd3mVCHzKIBgATwYlnSe7Flv4l4n8wQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1683346680; x= 1683433080; bh=cgbOS+7invuWPF/9WinZCthXBd3LjpGpyKaLrw20mN4=; b=i OyotNz74tqCvJziHhJGVfALNXN+ohn6mokRFrAmUzngvNLdFL7RV45FHICh7EJIZ CuMmTCDZS1nCTtGQ4IQxuvZkO7Wy6xk2Yh2ky15PJhs8B/+xwd9nKW8tfwDt1p7O iM+Yg+8DfTEeLtgeIl9l2SfDRKz3Tf1K1E5Ysr08uEIQNrKwbvAyvAOpXTsLOtxh IfU7rtm98JkEO/elBnUzQwaqb1zwYjqsCL9o6ksfnkENs4CByY/rGqsUEzTWIZmt J2wszLqhAxih6lHPiaAKkXPWN0FeRSTBW5kPqP6CB8ti3S3iYRFhopV+RG6c0WtT 0WG093/GE2RmODmcOl4ZQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeeffedgkedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttdefjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeetieetveevffeftddtudffueduleegveevhedvgeel tdfhtdeltdeghfeuleekieenucffohhmrghinhepmhhokhgruggsrdgtohhmnecuvehluh hsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhk lhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 6 May 2023 00:17:59 -0400 (EDT) Message-ID: Date: Fri, 5 May 2023 21:17:58 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: Death postgres To: Marc Millas , "pgsql-general@lists.postgresql.org" References: Content-Language: en-US From: Adrian Klaver 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 5/5/23 18: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. The result of EXPLAIN would be helpful. > > What are the cases where postgres may grow without caring about > temp_file_limit ? > > thanks, > > > > > Marc MILLAS > Senior Architect > +33607850334 > www.mokadb.com > -- Adrian Klaver adrian.klaver@aklaver.com