| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "Ghiurea, Isabella" <Isabella(dot)Ghiurea(at)nrc-cnrc(dot)gc(dot)ca>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Re: DB size value different than "/data" dir size |
| Date: | 2025-08-13 05:09:21 |
| Message-ID: | 9ee3e2fe636951642e21fc6645b6c16f25ee8d8e.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, 2025-08-11 at 14:13 +0000, Ghiurea, Isabella wrote:
> I believe this is related to VACUUM FULL behavior in a streaming replication 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 not the actual sum of
> /var/lib/pgsql/data1 files +dir size on the active PG were vacuum full reclaim the space.
>
> Is this a normal behavior in PG with reporting incorrect db size 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabrice Chapuis | 2025-08-13 10:06:15 | Re: pg_split_walfile_name |
| Previous Message | Bruce Momjian | 2025-08-12 17:34:56 | Re: pg_split_walfile_name |