pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: vrms <vrms@netcologne.de>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Maintenance
Date: Wed, 8 May 2024 16:28:55 +0200
Message-ID: <2323019d-ba9b-4eba-86e8-84b030bdd94a@netcologne.de> (raw)
In-Reply-To: <CANzqJaBf=f_CLxJO8MqN45z+KTY1i6hiF3Zt1mNX6Pmz66-JdQ@mail.gmail.com>
References: <CAEQOu1Fu2i7EoimtG_T4FQkuN5z3L5pY6n4jHHk=xB+NWZMfMw@mail.gmail.com>
	<8f36cff9-78aa-4e72-ab22-093a889a926d@gmx.net>
	<CANzqJaBf=f_CLxJO8MqN45z+KTY1i6hiF3Zt1mNX6Pmz66-JdQ@mail.gmail.com>


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

view thread (14+ messages)  latest in thread

Message-ID: <2323019d-ba9b-4eba-86e8-84b030bdd94a@netcologne.de>
Permalink:  ../2323019d-ba9b-4eba-86e8-84b030bdd94a@netcologne.de/
Also on:    postgresql.org/message-id/2323019d-ba9b-4eba-86e8-84b030bdd94a@netcologne.de

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: vrms@netcologne.de, pgsql-admin@lists.postgresql.org
  Subject: Re: Maintenance
  In-Reply-To: <2323019d-ba9b-4eba-86e8-84b030bdd94a@netcologne.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox