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 1jXl85-0002yw-3b for pgsql-bugs@arkaria.postgresql.org; Sun, 10 May 2020 12:32:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jXl83-0002gu-UE for pgsql-bugs@arkaria.postgresql.org; Sun, 10 May 2020 12:32:23 +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 1jXl83-0002gn-Nh for pgsql-bugs@lists.postgresql.org; Sun, 10 May 2020 12:32:23 +0000 Received: from mail-wm1-x344.google.com ([2a00:1450:4864:20::344]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jXl7x-0004Es-BB for pgsql-bugs@lists.postgresql.org; Sun, 10 May 2020 12:32:22 +0000 Received: by mail-wm1-x344.google.com with SMTP id e26so14818458wmk.5 for ; Sun, 10 May 2020 05:32:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=RN7RaBF55v5ZaoGvvmVdaT2FzNwYA0UC51GU8A346EI=; b=pLnGvaJ0I5LcyIJynypZ22+sy00qV0D3pQsf+VODJ74xi6JUbk2VHuG6Vj+LXNeqAm tucFu3JfBMOiooNVitv879CV6RawZBYcoFr32HmGzdE+ug+kOZ29Et74Z7kMXCyaCCHP GwuTqiZuuD7a3XSYYU4cobL6FF+AyjR9nSE10pBTVR1HTgYfW+9cuBqGbigdmuWv1I9M l4CWpi+lVgTcAXB4sTyX+g4Ij71n+MBobFsk++KJLOEtgvGdkK3zGsPowNCA1HMyUeJW yqGnarYoVB9paTBwbsV5KkejbUiw2aLqnT+yECOBZjoaCBdrWpvvyd8WQz2TenHcYtXy Epmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=RN7RaBF55v5ZaoGvvmVdaT2FzNwYA0UC51GU8A346EI=; b=GFCR2t++1KbZ6Gum4ald+hr4y7sL4s+vqVfHNXj21KhmG4FBcOBVBGi2kDmNE4J6mT t4ef4FVECj4DI+Tr25Ljy7vVKh/IPHnsw9zLhvhjyySmrB5/R6T/L9vy947rL4209CGo 2Pp+r5OY3PM5+zVVVs7e5PHTaTjnG/y8odEFd1ThDLcvwy1ITL6fF1/30ADI0V02vxod P6UpuHSUn8tNBCljjjtp+qnpr+EyD3tI7kaEAd6WTJToxgbnuME7fRuMThYcBmWhwat/ rH14NtL73zJl3kvpMqCeoUd30wJ2YhxOjbw2j+PNYsl9JEk8byghPfOOU1g8tPfzMl/E IFWQ== X-Gm-Message-State: AGi0PuZ/j9fAk7PH1qRtBjf3ACi3CWXvI0JdrklEZj0DqxTPCk7AiE/j aeDTPRNKG7xc0bq4s5pJY6XxOg== X-Google-Smtp-Source: APiQypKYk09T1+kqzD1gw1BMO5OkWvQJoFwKqQC5LvUqoPfWGtOwSUNYFzwzPTD8nNID2sPbpxYX1g== X-Received: by 2002:a7b:cb53:: with SMTP id v19mr25388099wmj.166.1589113936272; Sun, 10 May 2020 05:32:16 -0700 (PDT) Received: from localhost (ip-86-49-253-141.net.upcbroadband.cz. [86.49.253.141]) by smtp.gmail.com with ESMTPSA id j2sm12860168wrp.47.2020.05.10.05.32.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 10 May 2020 05:32:15 -0700 (PDT) Date: Sun, 10 May 2020 14:32:13 +0200 From: Tomas Vondra To: murali.natti@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16427: pgsql_tmp - temp files not released Message-ID: <20200510123213.mhhbcb3pg7iqmvce@development> References: <16427-c3dc404903609db5@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <16427-c3dc404903609db5@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sun, May 10, 2020 at 12:44:18AM +0000, PG Bug reporting form wrote: >The following bug has been logged on the website: > >Bug reference: 16427 >Logged by: Murali Natti >Email address: murali.natti@gmail.com >PostgreSQL version: 10.5 >Operating system: Red Hat Enterprise Linux Server release 6.10 (Sant >Description: > >Hello Team, > >We have observed a bug ( I guess ) that temporary files were not deleted >automatically even thought the respective PIDs are not running anymore. > >We couldn't take a chance to delete files manually so ended up with >restarting database to clear temp files. > >Is this know bug, what could be the reason for this? Can anyone please let >us know? > I don't think we're aware of any live bug in this area (although you're a couple of minor releases behind, and I haven't checked release notes between 10.5 and 10.12). I think you need to investigate what happened to the backends/commands that created the temporary files. Presumably it was interrupted or terminated in a way that prevented proper cleanup. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services