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 1s1S8q-00CPih-Ou for pgsql-general@arkaria.postgresql.org; Mon, 29 Apr 2024 14:38:04 +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 1s1S8n-0001AA-MP for pgsql-general@arkaria.postgresql.org; Mon, 29 Apr 2024 14:38:02 +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 1s1S8n-000192-Bv for pgsql-general@lists.postgresql.org; Mon, 29 Apr 2024 14:38:02 +0000 Received: from wfhigh7-smtp.messagingengine.com ([64.147.123.158]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s1S8k-000giA-L6 for pgsql-general@postgresql.org; Mon, 29 Apr 2024 14:38:01 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfhigh.west.internal (Postfix) with ESMTP id 3FDFF1800173; Mon, 29 Apr 2024 10:37:56 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 29 Apr 2024 10:37:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1714401475; x=1714487875; bh=ksaNnI2mNeHqn9EXoSkGOJSiYpF1Git0yDNRkmanvZA=; b= kIeQ2M3JuHSUlo3N2H40Ljt/ubcD+9NSl6GgeqWtjIvOSx/+2ryBa/gKtVhOTQJG X4fonZe/z5K/UlEO1C0Y4xqSquNL7JQXl2IuXY0cYawwt2Z9aptyQwamwX3IzLlF NR3KtmOyfc3l4i9ODzvrC/Raf5x3X4T3XDURUIQg/8nifCBrD3CP5mHQI1FF+s6W M801Mhg0doE9pUv0nJ5PjBxDUfOkmLZvr7F9mhJc49eYWvm4PUS7MNb/cFKqv9jF 6tzSegfYhDjDKR0WzfNdZLJAwFGpDb1dljTG8r+DYRKpoG9seUi77i+4nujYEMYZ gz3vP3YHD2NTNDEJjvHNJw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1714401475; x= 1714487875; bh=ksaNnI2mNeHqn9EXoSkGOJSiYpF1Git0yDNRkmanvZA=; b=W hsT4nEctqalIPE8y+TKXWc57TMlD7yO2a9T5r0N32sjM6sndNnpsjvEzKFjWsrmM FwEQt02PvfYqWlboUmzD6iDN5+buxwPGUtvRKN9kclgud+t//zc1t5z0bYnNCxEP ILrCDKF1jA2FtTjq9HHF0TrUFmRHmtJaP7NRksKqJygWJjGjFV3yUpAX87ZSshr+ 0+qYFzIPzjfN0gEDNY9BfiC+BdrcT9bgh1WuH1LgU2cagDQ4VVPjWENKpwiyqf2E W+az+iCI/aGBD/SI1pT3qtmJGvoAi3fuBfDGUGwec6aNzduQakUSWiMOTV4U5lJJ bzrVqOYLspC97KjdYg2/g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdduuddgjeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhevhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepueekhefhhffhfeehvddvueegueejvdejkeeffeeg leefiedvteejtdefveektdehnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrgh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughr ihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 29 Apr 2024 10:37:55 -0400 (EDT) Message-ID: <2fab499b-2f96-4b34-a4ea-4817c2414b4f@aklaver.com> Date: Mon, 29 Apr 2024 07:37:54 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Need help to make space on my database To: Cocam' server References: <5874a355-51fb-4fa3-acf4-df81a6d5b5f0@aklaver.com> Content-Language: en-US Cc: pgsql-general From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 4/29/24 07:33, Cocam' server wrote: Please reply to list also Ccing list > No, the aim is also to reallocate free space to the system for the other > tasks it performs.(That's why I said I'd like it returned to the OS) You led with: "I need help to make space on my database". How much current free space do you have available on the disk? Did you VACUUM FULL a table at a time or all of them at once? What are the individual tables sizes? > > Le lun. 29 avr. 2024 à 16:19, Adrian Klaver > a écrit : > > On 4/29/24 06:45, Cocam' server wrote: > > Hello. > > > > I need help to make space on my database. I have tables that are > several > > GB in size. I used to use the VACUUM FULL VERBOSE command; but > now, this > > command is too greedy in free space to be used and I'm looking > for a way > > to make free space (given back to the OS) > > > > Thanks in advance to everyone who responds > > Per > > https://www.postgresql.org/docs/current/sql-vacuum.html > > > "VACUUM reclaims storage occupied by dead tuples. In normal PostgreSQL > operation, tuples that are deleted or obsoleted by an update are not > physically removed from their table; they remain present until a VACUUM > is done. Therefore it's necessary to do VACUUM periodically, especially > on frequently-updated tables. > > <...> > > Plain VACUUM (without FULL) simply reclaims space and makes it > available > for re-use. This form of the command can operate in parallel with > normal > reading and writing of the table, as an exclusive lock is not obtained. > However, extra space is not returned to the operating system (in most > cases); it's just kept available for re-use within the same table. > " > > So a regular VACUUM should work if all you want to do is give the > database the ability to recycle the vacuumed tuple space. > > -- > Adrian Klaver > adrian.klaver@aklaver.com > -- Adrian Klaver adrian.klaver@aklaver.com