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 1lrrkj-0005qe-Sh for pgsql-hackers@arkaria.postgresql.org; Sat, 12 Jun 2021 00:43:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lrrki-0007Yl-58 for pgsql-hackers@arkaria.postgresql.org; Sat, 12 Jun 2021 00:43:56 +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 1lrrkh-0007Yd-Po for pgsql-hackers@lists.postgresql.org; Sat, 12 Jun 2021 00:43:55 +0000 Received: from mail-io1-xd30.google.com ([2607:f8b0:4864:20::d30]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lrrkc-0006j0-Gh for pgsql-hackers@lists.postgresql.org; Sat, 12 Jun 2021 00:43:54 +0000 Received: by mail-io1-xd30.google.com with SMTP id q3so9784369iop.11 for ; Fri, 11 Jun 2021 17:43:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=3XKrFBOx26PoBFq2j6PJIqpTeg0cRRr/on64yjlAsXk=; b=mgHlT+J/t3B+4EPEYiTDdNww5obLusPypTBoQhl7kL3Jc9W4W8AEY/oqzPreBBVs98 bjggNmEE+pcergV8bY3qll3cArHbATVQurSfjyUoWhmCsMRZZ8UUDpNnwkPY0m5W9zpK 4PI8uHXmxPlUHVb6WwI4Z+kij62+eYhR1vJ+l9Ua+VTAfYCIc5UbJHKTfbFcFQn8LCD1 /cP++WR68gt5bIbf+NCkw4kMgEgh6YzPLcvO1A56EqS1QULOpaSlw93NpbbT4at9rB0K yuejU/H2AN0sRk0VqQ8/0Met/E0r6OArxJ9/1yvj/sNtD7wJtWyilPAemBj3qSmieJsq 74gg== 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:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=3XKrFBOx26PoBFq2j6PJIqpTeg0cRRr/on64yjlAsXk=; b=ow0msEpYXNnALnwQr7CADxVVyMTwbxLbJhSZcl8uiSoeDzxxPRK0F/Mh1dVdwc0B2n IRxGnSokrsq6TQmamUJTYq4x5AVAXMFvyuDwLgBINhutUNR6lwnHnjCZy+ARNEKL/kFS EHQWwsMbOFyNLXLtTRNHlCMIaIVsJxNNJjDcxPrMUZk0dnHaW6DZzWlvgP/ey19q7HBh Fg2sOG/qedG91PxtsDuu9DhNk58XU5ZC773gfQZCGJWJ83CYKp6rs419qg6Nxd1SfUdl atnxOdNre4DmyEbPtpWclegWj1l2i2lpvIqeVkR5XCcGKgthwVDkllErS/r0KeSE47dW YGYg== X-Gm-Message-State: AOAM533sf6hi+nsTPB3DcyyYO8Un/hhbkh6x7GfGkz36DhGlnhgV3jdn HT0TaV1By3PlEQU6qFW3C/iI5w== X-Google-Smtp-Source: ABdhPJyHxQyTM1mMZ+sczdTrPSV9NqAfeIfgkD92M/KZfZ/Ervr5U0oywgJ50z8psw/NYBlkDmSwgw== X-Received: by 2002:a6b:cf13:: with SMTP id o19mr5255067ioa.206.1623458629453; Fri, 11 Jun 2021 17:43:49 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id v1sm4201555ilo.81.2021.06.11.17.43.48 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Jun 2021 17:43:48 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 8932C8009D6; Fri, 11 Jun 2021 19:43:47 -0500 (CDT) Date: Fri, 11 Jun 2021 19:43:47 -0500 From: Justin Pryzby To: Euler Taveira Cc: Tomas Vondra , pgsql-hackers@lists.postgresql.org Subject: Re: cleanup temporary files after crash Message-ID: <20210612004347.GP16435@telsasoft.com> References: <20201028184252.5vpoe65kcfebbmmf@development> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Oct 31, 2020 at 09:01:15PM -0300, Euler Taveira wrote: > > > The current behavior is only useful for debugging purposes. On Wed, 28 Oct 2020 at 15:42, Tomas Vondra wrote: > > One thing I'm not sure about is whether we should have the GUC as > > proposed, or have a negative "keep_temp_files_after_restart" defaulting > > to false. But I don't have a very good justification for the alternative > > other than vague personal preference. On Sat, Oct 31, 2020 at 09:01:15PM -0300, Euler Taveira wrote: > I thought about not providing a GUC at all or provide it in the developer > section. I've never heard someone saying that they use those temporary > files to investigate an issue. Regarding a crash, all information is already > available and temporary files don't provide extra details. This new GUC is just to keep the > previous behavior. I'm fine without the GUC, though. Should this GUC be classified as a developer option, and removed from postgresql.sample.conf ? That was discussed initially in October but not since. On Wed, Oct 28, 2020 at 11:16:26AM -0300, Euler Taveira wrote: > It also has an undesirable behavior: you have to restart the service to > reclaim the space. BTW, that's not really true - you can remove the tempfiles while the server is running. The complainant in bug#16427 was being careful - which is good. I watch for and remove tempfiles older than 2 days. The worst consequence of removing a tempfile would be a failed query. -- Justin