Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t9deB-00BQ83-Mv for pgsql-general@arkaria.postgresql.org; Sat, 09 Nov 2024 05:04:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t9de8-00GBy4-JV for pgsql-general@arkaria.postgresql.org; Sat, 09 Nov 2024 05:04:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t9de8-00GBxv-8J for pgsql-general@lists.postgresql.org; Sat, 09 Nov 2024 05:04:28 +0000 Received: from mail-oi1-x22d.google.com ([2607:f8b0:4864:20::22d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t9de1-000xtU-7q for pgsql-general@lists.postgresql.org; Sat, 09 Nov 2024 05:04:28 +0000 Received: by mail-oi1-x22d.google.com with SMTP id 5614622812f47-3e602994635so2015586b6e.0 for ; Fri, 08 Nov 2024 21:04:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731128660; x=1731733460; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=c8bI85k1A6kK7VlVxJEobpmGc0J17dsTwXiyfyx+0ok=; b=npSy4Sl89GQ4HxV0zax1NppAgDKbqEAfkxueVrnJC+KpoWTrEbYd0lBwZE/MJNP/1U 74XZDjtHKlKcXOYtzQhwVJR8qRdyfNFZMvpfHAUkH4SDtDSaApiB1WS9UhEZvXeVWGwt 7cktwXRxelS3riMIv7sLrBAfk50PQ+m61pJrYZUpxfiVW4woDTi512VNoo3Yb+pjoGJD mas6o+vwQGEzJAO2REvsr7EBfDA0GWll2U60v2ZSj9cWgnpGyModvZeZgGYD6BRqLmvG PgsiOHChptQM+3XT7R7oj4fwyZioM6Phdo9Td3SsO8BzoKK7LVp11WUKppUfBhtq0DEj RxNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731128660; x=1731733460; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=c8bI85k1A6kK7VlVxJEobpmGc0J17dsTwXiyfyx+0ok=; b=ZW5TF+Ui2nFzky6MKKdNihlKoQze3nnK1bw9UNYLQLquUODmS93by/rtyispMeWJaI KZOfFtE49UT2UIKaBaP9Xl8mx/uam6Av671GcT6dfVSCzQi27484PNR8kbbqQ0U6LOqQ vCcNdlO7rdUPWaCa9JBaaZjuKpJu9L+hRDHwAeXj5zyapHA6PNQ97pa7yDmL7DWd69xm YtOdypbQL76HGKx6k5b5/caIfFnhNoKpIqTwqfWO81+VwmW3UweBgeED1JdaGjxvI6KV iJQgVzEcJlaxxOQdx0mEBJRqE+OYlyXjgFYuC1iUnyiIhO35/r7DLEUvWMaT7GbJMGaG jR7g== X-Gm-Message-State: AOJu0YxKnHzQwzyO7um//pi5U4FLsFDK/94r6xAbGqanxdq+nUOwx4Wp 8OHptfdSIN6Kge2XRMoySzo86XFMr6lVAxJkgUqNVXKRmRuJEqiXWq/EvQz+wI985mMoDJIk0IQ DkNKQm4GhH5ccrqMQIpgejiCAK+6DdGbr X-Google-Smtp-Source: AGHT+IEPnAGlASpLcDIaE2GOHPMRT20IXGmfJF6TCJgVn0ziloC74EfJtvUJWe44m4uaz3CoHwCweAOPuyCRyNjkr00= X-Received: by 2002:a05:6808:1701:b0:3e5:f7d8:b560 with SMTP id 5614622812f47-3e79468ee01mr6067134b6e.18.1731128660197; Fri, 08 Nov 2024 21:04:20 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Sat, 9 Nov 2024 00:04:09 -0500 Message-ID: Subject: Re: pgsql_tmp consuming most of the space. To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000da079e062673cc6d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000da079e062673cc6d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Nov 8, 2024 at 11:51=E2=80=AFPM jayesh thakare wrote: > Hi all, > > In one of our production environment.. > > pgsql_tmp is taking about half of the space in FS. > And temp files are from Jan 2024. > > Our data fs is about to reach 98% percent.. > > Kindly suggest us what should be done to resolve this issue? > Delete the pgsql_tmp file from *before* the last time the postmaster started. > pgsql_tmp contains temperorary files during sub query execution. Then why > files are not getting deleted automatically after query completion? > Queries crashing can cause it. What version of PG are you running? > What are parameters that can be tuned to solve such issues in future? > --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000da079e062673cc6d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Nov 8, 2024 at 11:51=E2=80=AFPM j= ayesh thakare <thakarejaye= sh700@gmail.com> wrote:
Hi all,

In one of our production environment.= .

pgsql_tmp is taking ab= out half of the space in FS.
And temp files are from= Jan 2024.

Our data fs i= s about to reach 98% percent..

Kindly suggest us what should be done to resolve this issue?

Delete the pgsql_tmp file from befo= re=C2=A0the last time the postmaster started.
=C2=A0
pgsql_tmp contains temperorary files during sub query execution. = Then why files are not getting deleted automatically after query completion= ?

Queries crashing can caus= e it.=C2=A0 What version of PG are you running?
=C2=A0
What are parameters that can be tuned to solve such issues in future?=



--
Death to <Redacted>, and butter sauce.
Don't boil me, I'= ;m still alive.
<Redacted> lobster!
--000000000000da079e062673cc6d--