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 1t9dR4-00BOrk-IJ for pgsql-general@arkaria.postgresql.org; Sat, 09 Nov 2024 04:50:57 +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 1t9dR0-00G2CC-5I for pgsql-general@arkaria.postgresql.org; Sat, 09 Nov 2024 04:50:54 +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 1t9dQz-00G2C3-Qh for pgsql-general@lists.postgresql.org; Sat, 09 Nov 2024 04:50:54 +0000 Received: from mail-qt1-x830.google.com ([2607:f8b0:4864:20::830]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t9dQw-000xnn-QE for pgsql-general@lists.postgresql.org; Sat, 09 Nov 2024 04:50:53 +0000 Received: by mail-qt1-x830.google.com with SMTP id d75a77b69052e-4611abb6bd5so18284911cf.1 for ; Fri, 08 Nov 2024 20:50:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731127850; x=1731732650; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=uymgZlCNOZXTCPqqcpsszIpEaa+E34zQzPe+dJE6oNw=; b=CzlDggqm5EGzN/ca1S8A0+ujh6sikjEA5S78D8qxgn2l6OKePPsa5E9wymoJrZbmK9 kSXMYGgNNAvZTqQKA07gaYcCY/UGD9+Yqcakj9IhpCo5lPF3EIRzAYTlnbgFdo4Rflal Taro2xs5a8NagBEtev+ZEu8EPOaSUCORTTCoyBMiXWLNG8vi4ts87MIgBtm7V2mBVzNX 6uE/qgFw1D2TIzDfSJEv51tsMM8PRgGHslvnAWKbFuFV7mKP/LhUYtaLqA8yiGvqfn0i +OGRmBwq6r7UMEA7pjqueedl2YgEMq+xHt8W75pwSoYjlPeMZgvE8PUINlqL/bvZ7fkG RaPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731127850; x=1731732650; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=uymgZlCNOZXTCPqqcpsszIpEaa+E34zQzPe+dJE6oNw=; b=X7WVXiV2UnI+bEBroIMR5M6X3f3ttH2+2RAi2hzO7ULbWFzDSQXrpYGdaah8fsLqp3 YP6RTCH/Lzr4Q8n7GojvDs9RdFfgb71PTB0MwquW8NAaXhvCVQwWccCrsl7HDrXr3T8b 7o0Ak9so4T3J/y4hNAeFvFccfFXx6ytw5UW0gRywXBcRsXFuHWGDwu5STtqg889meUqd DEiX8rthw2PsEjDztVMX982jEDZD+8HMXcj1wH9pVRSMVYY0CAAXa+cnlyJPG+Q3x6BZ /LWMq0cuMH9WvXcM7KGkaFWvgoMXqI17qf0rUWij8dwtJ1lWzVHaTCBeaR9LacG80Zp6 BpMQ== X-Gm-Message-State: AOJu0YwbrnCFWRXQEljQE51P5f/OyviqgRS+LVkNhCCchDrohpXUgppX q6hN16ZfLrDQYhC4oN/lkrJosNhZExV5X7iEaXrFLzrbNXaNrLMAmWPKpuD3+90oLjsg2JEpmi5 CMc4uXIZBa+IIrOScRaS8Hs3plVSCRQ== X-Google-Smtp-Source: AGHT+IEkYWpGPWDrUyx9hDHfzNG1EhEYrJeH2IVZGGgKAbHNLGEvHQMUikWcaiC9DMYernswKf66gXZuKoADNowX4YI= X-Received: by 2002:a05:622a:8082:b0:463:16ee:bdb with SMTP id d75a77b69052e-46316ee0caamr19959101cf.23.1731127850328; Fri, 08 Nov 2024 20:50:50 -0800 (PST) MIME-Version: 1.0 From: jayesh thakare Date: Sat, 9 Nov 2024 10:10:44 +0530 Message-ID: Subject: pgsql_tmp consuming most of the space. To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000946c310626739ce9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000946c310626739ce9 Content-Type: text/plain; charset="UTF-8" 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? pgsql_tmp contains temperorary files during sub query execution. Then why files are not getting deleted automatically after query completion? What are parameters that can be tuned to solve such issues in future? Regards, Jayeshthakare Postgresql dba Clover infotech --000000000000946c310626739ce9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

In o= ne 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 do= ne to resolve this issue?


pgsql_tmp contains temperorary files during s= ub query execution. Then why files are not getting deleted automatically af= ter query completion?

What are parameters that can be tuned to solve su= ch issues in future?


Regards,
Jayeshthakare
Postgresql dba
Clover infotech


--000000000000946c310626739ce9--