Message-ID: <9ee3e2fe636951642e21fc6645b6c16f25ee8d8e.camel@cybertec.at>
Subject: Re: Re: DB size  value different than  "/data"  dir size
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: "Ghiurea, Isabella" <Isabella.Ghiurea@nrc-cnrc.gc.ca>,
 "pgsql-admin@postgresql.org"
	 <pgsql-admin@postgresql.org>
Date: Wed, 13 Aug 2025 07:09:21 +0200
In-Reply-To: <ea8a8186d36e4321ada5886c7bf66f3a@nrc-cnrc.gc.ca>
References: <aa68b26ba58b43c980648d76c27f4ce9@nrc-cnrc.gc.ca>
	,<9e1ebefd12e1fc955eee580caca5e9c37fd005ca.camel@cybertec.at>
	 <ea8a8186d36e4321ada5886c7bf66f3a@nrc-cnrc.gc.ca>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-1.fc42) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/9ee3e2fe636951642e21fc6645b6c16f25ee8d8e.camel%40cybertec.at>
Precedence: bulk

On Mon, 2025-08-11 at 14:13 +0000, Ghiurea, Isabella wrote:
> I believe this is related to VACUUM FULL behavior in a streaming replicat=
ion cfg ,
> for the standby server the space is not been reclaimed , But the sieze of=
 db reported
> with pg_pretty_db_size is identical on both db size but is=C2=A0 not the =
actual sum of
> /var/lib/pgsql/data1 files=C2=A0+dir size on the active PG were vacuum fu=
ll reclaim the space.
>=20
> Is this a normal behavior=C2=A0 in PG=C2=A0with reporting incorrect db si=
ze if vacuum full has
> not reclaim the OS disk space on both server?

VACUUM (FULL) will also reclaim the size on the standby.
There can be some delay in the case of a replication conflict.

Yours,
Laurenz Albe