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 1s4iJE-000TsD-0n for pgsql-admin@arkaria.postgresql.org; Wed, 08 May 2024 14:30:16 +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 1s4iID-001GUw-LU for pgsql-admin@arkaria.postgresql.org; Wed, 08 May 2024 14:29:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s4iID-001GUn-8R for pgsql-admin@lists.postgresql.org; Wed, 08 May 2024 14:29:13 +0000 Received: from cc-smtpout3.netcologne.de ([2001:4dd0:100:1062:25:2:0:3]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s4iIA-0001zb-0r for pgsql-admin@lists.postgresql.org; Wed, 08 May 2024 14:29:11 +0000 Received: from cc-smtpin3.netcologne.de (cc-smtpin3.netcologne.de [89.1.8.203]) by cc-smtpout3.netcologne.de (Postfix) with ESMTP id D57D0124D7 for ; Wed, 8 May 2024 16:29:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1715178545; bh=BLu/JaBJLIPmMRgFz71vWycqwhn8TRHCrIfoJvcpkEU=; h=Message-ID:Date:Subject:To:References:From:In-Reply-To:From; b=Ukx7N8rjyrx7N9P1KgvjdDUqDj5zy89w4gvDzfGdQz7UQR+MqUT9QYsHgJDWae1r3 WTTV1NyLXnmxjuoIIKlnNU3Pd0F4DVvQG5NjX5XRGD0LwYSAcRmFTZCj89heE7qEzy IiVxLJSxilM7YsLXvkIrkyt7xwHjzXZn9VtdqREO+KhE6GkQxoygI9qIscylLzKIPH ZbEe0n96P7ti6IyytuaAPFKGd9EF7hN5qRV+vd5zp3EfxCdAktXUmO+taVRpd5ygLa 39krdVO0reTNV0RnTQaGra8a6g2TFBG7n2PE2evKMsyr6ehQgqikysZTT7VTbXTW5c tvPj2GVexq/OQ== Received: from [IPV6:2a03:b580:aa39:a501:cc7c:e623:8a1a:4e0b] (unknown [IPv6:2a03:b580:aa39:a501:cc7c:e623:8a1a:4e0b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by cc-smtpin3.netcologne.de (Postfix) with ESMTPSA id A27DA11DC9 for ; Wed, 8 May 2024 16:29:05 +0200 (CEST) Content-Type: multipart/alternative; boundary="------------Y8j0dL5YFB6LE8gI40aMy5k0" Message-ID: <2323019d-ba9b-4eba-86e8-84b030bdd94a@netcologne.de> Date: Wed, 8 May 2024 16:28:55 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Maintenance To: pgsql-admin@lists.postgresql.org References: <8f36cff9-78aa-4e72-ab22-093a889a926d@gmx.net> Content-Language: en-US From: vrms In-Reply-To: X-NetCologne-Spam: L X-Rspamd-Action: add header X-Rspamd-Queue-Id: A27DA11DC9 X-Spamd-Bar: - X-Rspamd-Pre-Result: action=add header; module=force_actions; unknown reason List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------Y8j0dL5YFB6LE8gI40aMy5k0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 5/8/24 3:10 PM, Ron Johnson wrote: > Don't dead tuples have to be vacuumed away before the space can be reused? I think that is correct. As per my understanding ... VACUUM    - removes dead tuples and makes the consumed space available for future data    - does not free disk space    - does not cause any locks VACUUM FULL    - removes dead tuples and frees actual disk space    - causes locks on the table being VACUUMed --------------Y8j0dL5YFB6LE8gI40aMy5k0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 5/8/24 3:10 PM, Ron Johnson wrote:

> Don't dead tuples have to be vacuumed away before the space can be reused?

I think that is correct. As per my understanding ...

VACUUM

   - removes dead tuples and makes the consumed space available for future data
   - does not free disk space
   - does not cause any locks

VACUUM FULL

   - removes dead tuples and frees actual disk space
   - causes locks on the table being VACUUMed
--------------Y8j0dL5YFB6LE8gI40aMy5k0--