Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Re: Observation with Postgres table size
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <DB4PR10MB7469DCC3427E61FEEE2F8D6F8CE72@DB4PR10MB7469.EURPRD10.PROD.OUTLOOK.COM>
Date: Fri, 10 May 2024 08:00:51 -0600
Cc: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A261A0D0-9868-4096-8F64-C966C8DB129C@elevated-dev.com>
References: 
 <DB4PR10MB7469DCC3427E61FEEE2F8D6F8CE72@DB4PR10MB7469.EURPRD10.PROD.OUTLOOK.COM>
To: Sabyasachi Mukherjee <mukherjee.sabyasachi@outlook.com>
Archived-At: 
 <https://www.postgresql.org/message-id/A261A0D0-9868-4096-8F64-C966C8DB129C%40elevated-dev.com>
Precedence: bulk

> On May 10, 2024, at 7:57=E2=80=AFAM, Sabyasachi Mukherjee =
<mukherjee.sabyasachi@outlook.com> wrote:
>=20
> Can any body please advise, how to reduce the size of the table?

VACUUM FULL

Read the docs to understand what it does. Deleting a row does not shrink =
the table.=20

Think about it, what happens when you delete a row that's first in the =
file on disk? Do you expect the rest of the table to be rewritten? Do =
you expect the file to be rewritten every time a row is deleted? On =
commit of any transaction that included a delete?

Postgres will eventually reuse the space left behind by deleted rows =
(read the docs for VACUUM), so under most use cases this is not a =
problem.=