public inbox for [email protected]  
help / color / mirror / Atom feed
From: Greg Sabino Mullane <[email protected]>
To: KK CHN <[email protected]>
Cc: [email protected]
Subject: Re: Pgbackrest info output interpretation
Date: Fri, 14 Nov 2025 08:48:57 -0500
Message-ID: <CAKAnmmLUE=BmgBbkqFp9nuQd95PxHAxx=R3Q_WH2YLT_vYg4YA@mail.gmail.com> (raw)
In-Reply-To: <CAKgGyB-4HmSMCg8L1_HCvK6jF=-bJtxn9v4oCH-jY0EdzKH-Lw@mail.gmail.com>
References: <CAKgGyB-4HmSMCg8L1_HCvK6jF=-bJtxn9v4oCH-jY0EdzKH-Lw@mail.gmail.com>

The "database size" is going to be your data directory, MINUS your pg_wal
directory, MINUS unlogged/temp relations, and MINUS things that are not
needed for recovery (i.e. all the small pg_ directories such as
pg_subtrans). The "database backup size" is how much of that 3GB is part of
*this* backup - for a full backup, the number will be the same, for diff or
incr, it will be a lot less. The "repo backup size" on the last line is the
compressed size of the previous "database backup size"

How to correlate the pgbackrest ( info) database size, database backup size
> and repo1 backup size     and actual du output on DB cluster.
>

You cannot, really, without deep knowledge of things like which files on
disk map back to unlogged tables. However, du on the datadir minus all pg_
dirs should get you in the ballpark. As a quick example:

cd $DATADIR
du --summarize * | awk '!/pg_/{x=x+$1}END{print x}' | numfmt --to=iec

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support


view thread (2+ messages)

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Pgbackrest info output interpretation
  In-Reply-To: <CAKAnmmLUE=BmgBbkqFp9nuQd95PxHAxx=R3Q_WH2YLT_vYg4YA@mail.gmail.com>

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

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