On Sat, Nov 15, 2025 at 7:16 AM Marcel Menzel wrote:
> For the PostgreSQL upgrade to version 18, I took the opportunity to test
> the reflink support in pg_upgrade (with --clone) on OpenZFS 2.3.4 /
> Linux 6.15.11 and it worked flawlessly, being a huge time saver here.
Nice!
> I've looked into t
Hello List,
For the PostgreSQL upgrade to version 18, I took the opportunity to test
the reflink support in pg_upgrade (with --clone) on OpenZFS 2.3.4 /
Linux 6.15.11 and it worked flawlessly, being a huge time saver here.
I've looked into the documentation for pg_upgrade and it's only
menti
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
./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
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: 000100050024 /
000100050024
database size: 3GB, database backup size: 3GB
repo1: backup size: 431.0MB
