From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: murali.natti@gmail.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16427: pgsql_tmp - temp files not released
Date: Sun, 10 May 2020 14:32:13 +0200
Message-ID: <20200510123213.mhhbcb3pg7iqmvce@development> (raw)
In-Reply-To: <16427-c3dc404903609db5@postgresql.org>
References: <16427-c3dc404903609db5@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tomas.vondra@2ndquadrant.com, murali.natti@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16427: pgsql_tmp - temp files not released
In-Reply-To: <20200510123213.mhhbcb3pg7iqmvce@development>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox