Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vJpAa-004BDS-1p for pgsql-general@arkaria.postgresql.org; Fri, 14 Nov 2025 08:28:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vJp9Y-005Ack-3C for pgsql-general@arkaria.postgresql.org; Fri, 14 Nov 2025 08:27:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vJp9Y-005Acc-24 for pgsql-general@lists.postgresql.org; Fri, 14 Nov 2025 08:27:32 +0000 Received: from mail-yw1-x1136.google.com ([2607:f8b0:4864:20::1136]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vJp9W-007gQl-1x for pgsql-general@lists.postgresql.org; Fri, 14 Nov 2025 08:27:32 +0000 Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-71d71bcab69so15247007b3.0 for ; Fri, 14 Nov 2025 00:27:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1763108848; x=1763713648; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=w/qybtYfWveApBkkYtHyS+phpmpOY0QHY054cz0qdw0=; b=OrrowUVvRdtCQd38nTrD/kARo6wJ5gQtSD/9S/AG164bSV4z9xqIINtKT9jeATpM5v BcUpI+0Rp+sz+P61260aSLyGD9pFq+wE90xueJMhMw3K1Vz0Aa1cDBeaWnB81xoPnH2g 3BjqOLZxxG2tC8mViWqR3GDbZ5as6xXFDp5z15yRedhXhDWTgflAtQKe+rN2b0k+PMWt fow4pcKuS7bDkD0hn4PTG20R7pS5rsfJXoHqKGA0EsdwgvwmlhM6+YcbRJ6eowQL+3EH /x/0azwrzLPmwIDQV1ksfPuFARqANCV48eLIG20IbZBu9/JgEPTWwMOiJW2M8pPqtySg UD9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763108848; x=1763713648; h=to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=w/qybtYfWveApBkkYtHyS+phpmpOY0QHY054cz0qdw0=; b=LLoMs1J2iRo4h2Kk9VML+OnHCP2SX1V/9uiTN6taP30Y4hmjQXg4ku0itOVlCqXPYH SQbOpifpRqzdzUL63D3IkpZtWp50VecLZoaAdhbcJEaTV5cWpZziox4RX/PbbPGdkXKZ V0TMRGczEau4hHjkxv8YklYqLH9AwmdVjH1WsUqW8KJmE250WRSyi/S1tr4K++SCROkb LlWQi3HG5d/p0CJ++u10vD3epJKg9XlRe/kkxMCUzmiIIsGzqJF+4OkRyouD4/3RzgPA tktTOGSlcAnBnLOuW8MjqzQK1Iaw88X2BpG2AhbTUf5xYczPbGm2rq7112g4S9uMVYNu O+aw== X-Gm-Message-State: AOJu0Yzsl0OXrV+0q3KTtPO7Rue6n4JAFPVEMGOy4/eybY6sSvTIVlFz PqfS61LmxcYS7y0FrAOjZu/UUIF4XorEi8GVENj8Vz8zqc/Zyun985KvQz2j/sqhlNAUPTubN5d TSu6KdnM2knC0en1M+mXN2nmJHzNXeH9MuEgF X-Gm-Gg: ASbGncuLQmAyBhUv8h2JALoRPKkZj65B/h39YwxzHjbiyGANqbOCNb78XwqwbZBgJcR +4lP2sOb+FM27KQqSACxvUAjPRTYgK+vE8P1N62sLVm47HAsnst2loNkh2w4tWjASGTPrT1hkNi Gfz7ZY9l8pePhEj0cyBR9Lee3m/AqTW4aVwsaxx6GQxMrtOG0kfvxfgbsrL/X3h0eCb792leo/K lz4dVq5DQTasXEiouDi8do5lkZMiOZyImIy0TW1wTaAwwq2GlY4z7B0Q5KoHQ== X-Google-Smtp-Source: AGHT+IFx/aE+evItlbXOipRDTdZScH8Cs2+F1TFNP/2PCJBsFDLTG0ats2sqaJhlX/nS/KedirWk27VmPr6TVEpLzkw= X-Received: by 2002:a53:b411:0:b0:63f:aef7:d009 with SMTP id 956f58d0204a3-641e74dc962mr1487650d50.5.1763108848025; Fri, 14 Nov 2025 00:27:28 -0800 (PST) MIME-Version: 1.0 From: KK CHN Date: Fri, 14 Nov 2025 14:02:38 +0530 X-Gm-Features: AWmQ_blPuekJn-_COoJyxbSfj7WuRXHZ1zzUR6dn4f15-c2e0OW6jwcPxHEJ55c Message-ID: Subject: Pgbackrest info output interpretation To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000964236064389c4f0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000964236064389c4f0 Content-Type: text/plain; charset="UTF-8" Hi, I am having confusion trying to understand the database size, backupsize and repo backup size.. In my DB server I have du output as follows. /data/edb/as16 [root@db1 as16]# du -h -d 1 5.3G ./data 25G ./tablespace 30G . [root@db1 as16]# On my Repo Server pgbackest info says .... full backup: 20251114-121504F timestamp start/stop: 2025-11-14 12:15:04+05:30 / 2025-11-14 12:20:58+05:30 wal start/stop: 000000010000000500000024 / 000000010000000500000024 database size: 3GB, database backup size: 3GB repo1: backup size: 431.0MB Could someone shed some light on 431 MB and database size:3GB, database backup size : 3GB compared to the DB cluster on disk usage output ? How to correlate the pgbackrest ( info) database size, database backup size and repo1 backup size and actual du output on DB cluster. Note: I am using zst compression on pgbackrest Regards, Krishane --000000000000964236064389c4f0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,=C2=A0 =C2=A0 =C2=A0

I am having con= fusion trying to understand=C2=A0the database size, backupsize and repo bac= kup size..

In my DB server I have du output as fol= lows.

/data/edb/as16
[root@db1 as16]# du -h -d 1
5.3G = =C2=A0 =C2=A0./data
25G =C2=A0 =C2=A0 ./tablespace
30G =C2=A0 =C2=A0 = .
[root@db1 as16]#

On my Repo Server pgbackest info sa= ys ....=C2=A0

full backup: 20251114-121504F
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 timestamp start/stop: 2025-11-14 12:= 15:04+05:30 / 2025-11-14 12:20:58+05:30
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 wal start/stop: 000000010000000500000024 / 000000010000000500000= 024
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 database size: 3GB, databa= se backup size: 3GB
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 repo1: bac= kup size: 431.0MB

Could someone shed some light on=C2=A0 =C2=A0 431 = MB and database size:3GB, database backup size : 3GB=C2=A0 compared to the = DB cluster on disk usage output ?

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

Note: I am = using zst compression=C2=A0on pgbackrest=C2=A0

Regards,
Krishane=C2=A0
--000000000000964236064389c4f0--